Dear All,
We are using 3.8.x kernel on ARM, We are facing soft lockup issue.
Following are the logs.
BUG: spinlock lockup suspected on CPU#0, process1/525
lock: 0xd8ac9a64, .magic: dead4ead, .owner: /-1, .owner_cpu: -1
1 . Looks like lock is available as owner is -1, why arch_spin_trylock
is
On Fri, Jan 17, 2014 at 02:00:32PM -0700, Bjorn Helgaas wrote:
> > As the release is supposedly this weekend, do you prefer
> > the patches to go to your tree or to individual trees after
> > the release?
>
> I'd be happy to merge them, except for the fact that they probably
> wouldn't have any
> On Fri, 2014-01-17 at 22:49 -0800, Eric Dumazet wrote:
> > On Fri, 2014-01-17 at 17:25 -0800, dormando wrote:
> > > Hi,
> > >
> > > Upgraded a few kernels to the latest 3.10 stable tree while tracking down
> > > a rare kernel panic, seems to have introduced a much more frequent kernel
> > >
On Fri, 2014-01-17 at 22:49 -0800, Eric Dumazet wrote:
> On Fri, 2014-01-17 at 17:25 -0800, dormando wrote:
> > Hi,
> >
> > Upgraded a few kernels to the latest 3.10 stable tree while tracking down
> > a rare kernel panic, seems to have introduced a much more frequent kernel
> > panic. Takes
On Saturday 11 January 2014 13:55:15 Marc Kleine-Budde wrote:
> On 01/11/2014 07:31 PM, Randy Dunlap wrote:
> > On 01/11/2014 10:09 AM, Marc Kleine-Budde wrote:
> >> Hello,
> >>
> >> in current linux-next (and net-next) the compilation of the CAN
> >>
> >> drivers[1] with ARCH=blackfin fails
On Fri, Jan 17, 2014 at 11:08 PM, J. Bruce Fields wrote:
> On Fri, Jan 17, 2014 at 11:53:07PM +1300, Michael Kerrisk (man-pages) wrote:
>> >The following additional errors are defined for renameat2():
>> >
>> >EOPNOTSUPP
>> > The filesystem does not support a flag in
On Fri, 2014-01-17 at 17:25 -0800, dormando wrote:
> Hi,
>
> Upgraded a few kernels to the latest 3.10 stable tree while tracking down
> a rare kernel panic, seems to have introduced a much more frequent kernel
> panic. Takes anywhere from 4 hours to 2 days to trigger:
>
> <4>[196727.311203]
Freescale IFC controller has been used for mpc8xxx. It will be used
for ARM-based SoC as well. This patch moves the driver to driver/memory
and fix the header file includes.
Also remove module_platform_driver() and instead call
platform_driver_register() from subsys_initcall() to make sure
As Freescale IFC controller has been moved to driver to driver/memory.
So enable memory driver in powerpc config
Signed-off-by: Prabhakar Kushwaha
---
Changes for v2: Sending as it is
Changes for v3: Sending as it is
Changes for v4: Rebased to
In trying to track down a bug (see below), I noticed that
math_state_restore() in arch/x86/kernel/traps.c appears to unconditionally
disable interrupts when called. Is this intended behavior or a bug?
The bug in question is triggered by dumping core on an ecryptfs file
system when
On 01/17/2014 10:28 PM, Eric Dumazet wrote:
On Fri, 2014-01-17 at 17:42 +0800, Jason Wang wrote:
Many qdiscs can queue a packet for a long time, this will lead an issue
with zerocopy skb. It means the frags will not be orphaned in an expected
short time, this breaks the assumption that
On 10:59 Fri 17 Jan , Bo Shen wrote:
> In sama5d3 SoC, there are 16 endpoints. As the USBA_NR_ENDPOINTS
> is only 7. So, fix it for sama5d3 SoC using the udc->num_ep.
>
> Signed-off-by: Bo Shen
> ---
>
> drivers/usb/gadget/atmel_usba_udc.c | 2 +-
> 1 file changed, 1 insertion(+), 1
Signed-off-by: SeongJae Park
---
drivers/gpio/gpio-mcp23s08.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-mcp23s08.c b/drivers/gpio/gpio-mcp23s08.c
index b16401e..97198ef 100644
--- a/drivers/gpio/gpio-mcp23s08.c
+++ b/drivers/gpio/gpio-mcp23s08.c
@@
On Sat, Jan 18, 2014 at 7:11 AM, Linus Walleij wrote:
> On Fri, Jan 17, 2014 at 6:43 PM, Chen-Yu Tsai wrote:
>> On Sat, Jan 18, 2014 at 12:47 AM, Arnd Bergmann wrote:
>
+- NAME_shutdown-gpios : GPIO phandle to shutdown control
+ (phandle must be the second)
Linus,
Al Viro has concerns with the trace_pipe release method calling
__free_page() instead of using the generic_pipe_buf_release() which
does a page_cache_release(). Looking at the differences between
__free_page() and page_cache_release() I do not think there's a real
issue here. But to be on
Hi,
I encountered the same problem with another device.
If possible, it would be nice to pick Marius's patch for stable
kernels (tested here on v3.12.6).
There are chances that MacOSX is affected by a similar issue,
so if anybody has friends there...
Thanks,
--
Jérôme
On Wed, 8 Jan 2014
On 2014-1-17 22:12, Will Deacon wrote:
> On Fri, Jan 17, 2014 at 12:24:58PM +, Hanjun Guo wrote:
>> Introduce arm_core.c and its related head file, after this patch,
>> we can get ACPI tables from firmware on ARM64 now.
>>
>> Signed-off-by: Al Stone
>> Signed-off-by: Graeme Gregory
>>
On 2014-1-18 11:45, Hanjun Guo wrote:
> On 2014-1-17 20:06, Sudeep Holla wrote:
>> On 17/01/14 02:03, Hanjun Guo wrote:
>>> Move idle_boot_override out of the arch directory to be a single enum
>>> including both platforms values, this will make it rather easier to
>>> avoid ifdefs around which
On 1/17/2014 10:38 PM, Kumar Gala wrote:
On Jan 15, 2014, at 11:42 PM, Prabhakar Kushwaha
wrote:
Freescale IFC controller has been used for mpc8xxx. It will be used
for ARM-based SoC as well. This patch moves the driver to driver/memory
and fix the header file includes.
Also remove
Hi yinghai,
Sorry for the noise. I didn't noticed Rafael's work,
so I generated this patchset when encountered this issue
during testing PCI host bridge hotplug. It should achieve
the same goal.
Thanks!
Gerry
On 2014/1/18 11:23, Yinghai Lu wrote:
> ACPI / hotplug: Make ACPI PCI root
Allow drivers to be compiled as modules by exporting more clock
provider functions.
Reported-by: kbuild test robot
Signed-off-by: Stephen Boyd
---
drivers/clk/clk.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 0b27b543dacf..2e83cf643db0
On 2014-1-17 20:06, Sudeep Holla wrote:
> On 17/01/14 02:03, Hanjun Guo wrote:
>> Move idle_boot_override out of the arch directory to be a single enum
>> including both platforms values, this will make it rather easier to
>> avoid ifdefs around which definitions are for which processor in
>>
Hi,
On Sat, Jan 18 2014, Andrew Bresticker wrote:
There's an existing patch for that...
http://www.spinics.net/lists/arm-kernel/msg296596.html
>>>
>>> Ah, I see. Looks like it has yet to be picked up...
>>
>> The patches aren't quite identical -- Andrew's leaves the
>> disable_irq()
On 01/17/2014 04:12 PM, r...@redhat.com wrote:
> From: Rik van Riel
>
> The current code in task_numa_placement calculates the difference
> between the old and the new value, but also temporarily stores half
> of the old value in the per-process variables.
>
> The NUMA balancing code looks at
On Fri, 2014-01-17 at 18:23 +0100, Sebastian Andrzej Siewior wrote:
> So I had rtmutex-take-the-waiter-lock-with-irqs-off.patch in my queue
> which took the waiter lock with irqs off. This should be the same thing
> you try do here.
(yeah, these are just whacked mole body bags;)
--
To
On Fri, 2014-01-17 at 18:14 +0100, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2013-12-25 18:37:37 [+0100]:
>
> >On Tue, 2013-12-24 at 23:55 -0800, Paul E. McKenney wrote:
> >> On Wed, Dec 25, 2013 at 04:07:34AM +0100, Mike Galbraith wrote:
> >
> >Having sufficiently recovered from
1) The value choosen for the new SO_MAX_PACING_RATE socket option on
parisc was very poorly choosen, let's fix it while we still can.
From Eric Dumazet.
2) Our generic reciprocal divide was found to handle some edge cases
incorrectly, part of this is encoded into the BPF as deep as the
On Fri, Jan 17, 2014 at 6:48 PM, Jiang Liu wrote:
> Reuse ACPI hotplug framework to support PCI host bridge hotplug, this
> makes PCI host bridge hotplug implementation simpler and more clear.
>
> It also fixes a bug in support of PCI host bridge hot-addition.
> Currently pci_root driver fails to
On Fri, Jan 17, 2014 at 3:40 PM, Chris Ball wrote:
> Hi, adding Aisheng,
>
> On Fri, Jan 17 2014, Andrew Bresticker wrote:
>> On Fri, Jan 17, 2014 at 3:11 PM, John Tobias
>> wrote:
>>> There's an existing patch for that...
>>> http://www.spinics.net/lists/arm-kernel/msg296596.html
>>
>> Ah, I
On Fri, 2014-01-17 at 18:00 +0100, Sebastian Andrzej Siewior wrote:
> * Mike Galbraith | 2013-12-24 16:47:47 [+0100]:
>
> >I built this kernel with Paul's patch and NO_HZ_FULL enabled again on 64
> >core box. I haven't seen RCU grip yet, but I just checked on it after
> >3.5 hours into this
From: Stephen Warren
Date: Fri, 17 Jan 2014 12:29:24 -0700
> From: Stephen Warren
>
> It's now built as a separate utility module, and enabling BT selects
> that module in Kconfig. This fixes:
...
> (this change probably simply wasn't "git add"d to a53d34c3465b)
>
> Fixes: a53d34c3465b
From: Tejun Heo
Date: Fri, 17 Jan 2014 13:11:52 -0500
> net_cls and net_prio are the only cgroups which are allowed to be
> built as modules. The savings from allowing the two controllers to be
> built as modules are tiny especially given that cgroup module support
> itself adds quite a bit of
From: Tejun Heo
Date: Fri, 17 Jan 2014 13:11:54 -0500
> Signed-off-by: Tejun Heo
Acked-by: David S. Miller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Christoph Lameter
Date: Fri, 17 Jan 2014 09:18:36 -0600
> [Patch depends on another patch in this series that introduces raw_cpu_ops]
>
> Replace uses of get_cpu_var for address calculation through this_cpu_ptr.
>
> Cc: "David S. Miller"
> Cc: net...@vger.kernel.org
> Cc: Eric Dumazet
From: Christoph Lameter
Date: Fri, 17 Jan 2014 09:18:29 -0600
> Acked-by: Ingo Molnar
> Signed-off-by: Christoph Lameter
Acked-by: David S. Miller
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo
On Fri, Jan 17, 2014 at 11:59:21AM -0800, Sherman Yin wrote:
> On 14-01-16 05:19 AM, Linus Walleij wrote:
> >On Sat, Dec 21, 2013 at 3:13 AM, Sherman Yin wrote:
> >
> >'> Adds pinctrl driver for Broadcom Capri (BCM281xx) SoCs.
> >>
> >>Signed-off-by: Sherman Yin
> >>Reviewed-by: Christian Daudt
Field 'ignore' in acpi_hotplug_profile is introduced by "ca499fc87ed945
ACPI / hotplug: Fix conflicted PCI bridge notify handlers" to support
PCI host bridge hotplug. Now it's useless, so kill it.
Signed-off-by: Jiang Liu
---
drivers/acpi/scan.c |2 +-
include/acpi/acpi_bus.h |1 -
Add callback prepare() into acpi_hotplug_handler, which will get called
at the very beginning of ACPI hotplug event handler. The ACPI core will
ignore the event if prepare() returns NOTIFY_STOP.
Signed-off-by: Jiang Liu
---
drivers/acpi/scan.c |4
include/acpi/acpi_bus.h |1 +
Reuse ACPI hotplug framework to support PCI host bridge hotplug, this
makes PCI host bridge hotplug implementation simpler and more clear.
It also fixes a bug in support of PCI host bridge hot-addition.
Currently pci_root driver fails to install notification handler for
PCI host bridge absent at
Konrad,
The following patch sets the bits in CR0 and CR4. Please note, I'm working
on patch for the xen side. The CR4 features are not currently exported
to a PVH guest.
Roger, I added your SOB line, please lmk if I need to add anything else.
This patch was build on top of
pvh was designed to start with pv flags, but a commit in xen tree
51e2cac257ec8b4080d89f0855c498cbbd76a5e5 removed some of the flags as
they are not necessary. As a result, these CR flags must be set in the
guest.
Signed-off-by: Roger Pau Monne
Signed-off-by: Mukesh Rathor
---
From: Randy Dunlap
Make KVM_MMU_AUDIT kconfig help text readable and collapse
two spaces between words down to one space.
Signed-off-by: Randy Dunlap
---
arch/x86/kvm/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- lnx-313-rc8.orig/arch/x86/kvm/Kconfig
+++
On Fri 2014-01-17 17:21:00, H. Peter Anvin wrote:
> On 01/17/2014 04:29 PM, Pavel Machek wrote:
> >
> > Have you checked your dmesg recently? Normal people don't read
> > it... it is just too much of it.
> >
> >> Printing a warning is appropriate if we can't actually fix the problem
> >> in the
From: Gerald Schaefer
Date: Thu, 16 Jan 2014 16:54:48 +0100
> commit ae4b46e9d "net: rds: use this_cpu_* per-cpu helper" broke per-cpu
> handling for rds. chpfirst is the result of __this_cpu_read(), so it is
> an absolute pointer and not __percpu. Therefore, __this_cpu_write()
> should not
On 01/17/2014 05:19 PM, Bjorn Helgaas wrote:
> On Fri, Jan 17, 2014 at 02:26:23PM -0500, Joseph Salisbury wrote:
>> On 01/17/2014 12:02 PM, Bjorn Helgaas wrote:
>>> On Thu, Jan 16, 2014 at 01:14:01PM -0500, Joseph Salisbury wrote:
On 01/16/2014 01:12 PM, Bjorn Helgaas wrote:
> On Thu, Jan
Hi,
Upgraded a few kernels to the latest 3.10 stable tree while tracking down
a rare kernel panic, seems to have introduced a much more frequent kernel
panic. Takes anywhere from 4 hours to 2 days to trigger:
<4>[196727.311203] general protection fault: [#1] SMP
<4>[196727.311224] Modules
On Thu, Jan 16, 2014 at 4:09 PM, Nicholas A. Bellinger
wrote:
>
> This change allows the percpu_ida tag allocator to optionally use
> interruptible sleep that iscsi-target expects, while still leaving the
> functionality + interface for existing percpu_ida consumers unchanged.
I'm not pulling
In the process IO direction, dio_refill_pages will call get_user_pages_fast
to map the page from user space. If ret is less than 0 and IO is write, the
function will create a zero page to fill data. This may work for some file
system, but in some device operate we prefer whole write or fail,
On 01/17/2014 04:29 PM, Pavel Machek wrote:
>
> Have you checked your dmesg recently? Normal people don't read
> it... it is just too much of it.
>
>> Printing a warning is appropriate if we can't actually fix the problem
>> in the OS. If we actually make the problem go away then we have just
On Fri, Jan 17, 2014 at 07:57:16PM -0500, Alan Ott wrote:
> On 01/17/2014 08:46 AM, Russell King - ARM Linux wrote:
>> My suspicion therefore is that some other thread must have died while
>> holding the mmap_sem, so there's probably a kernel oops earlier...
>> that's my best guess at the moment
Cc: Daniel Borkmann
On 2014/1/18 2:11, Tejun Heo wrote:
> net_cls and net_prio are the only cgroups which are allowed to be
> built as modules. The savings from allowing the two controllers to be
> built as modules are tiny especially given that cgroup module support
> itself adds quite a bit
arch/arm/boot/dts/include/dt-bindings/clock/qcom,mmcc-msm8974.h:60:0:
warning: "RBCPR_CLK_SRC" redefined
Rename this to MMSS_RBCPR_CLK_SRC to avoid conflicts with the
RBCPR clock in the gcc header.
Reported-by: Bjorn Andersson
Signed-off-by: Stephen Boyd
---
On 01/17/2014 08:46 AM, Russell King - ARM Linux wrote:
On Wed, Jan 15, 2014 at 08:13:04PM -0500, Alan Ott wrote:
So my questions are:
1. Why don't I see a full backtrace beyond the exception stack? It's the
same when dump_stack() is called manually.
No idea - it looks like you're not using
Test module for the simple algorithm load balancer
Signed-off-by: Tadeusz Struk
---
crypto/Kconfig|6 ++
crypto/Makefile |1 +
crypto/test_alg_loadbalance.c | 231 +
3 files changed, 247 insertions(+)
create mode
Hi,
In case of multiple crypto devices implementing the same algorithms
the arbitration, which one to use is based on the cra_priority.
Currently the algorithm with the highest priority is always be used.
In case of two algorithms with the same priority the one added last is used.
There is no load
On Fri 2014-01-17 14:51:52, H. Peter Anvin wrote:
> On 01/17/2014 02:50 PM, Borislav Petkov wrote:
> > On Fri, Jan 17, 2014 at 11:28:06PM +0100, Pavel Machek wrote:
> >> Would it make sense to printk() a warning?
> >
> > No because people come and start bitching about their dmesg containing
> > a
-Deny use of a char mtd device to map as block device.
-mutex_init when mtd structure is available.
-fixme applied : check device size is a multiple of erasesize.
-mutex_destroy on each device in block2mtd_exit and add_device failure.
Signed-off-by: Fabian Frederick
---
Hi, adding Aisheng,
On Fri, Jan 17 2014, Andrew Bresticker wrote:
> On Fri, Jan 17, 2014 at 3:11 PM, John Tobias wrote:
>> There's an existing patch for that...
>> http://www.spinics.net/lists/arm-kernel/msg296596.html
>
> Ah, I see. Looks like it has yet to be picked up...
The patches aren't
On 01/17/2014 04:13 PM, Linus Walleij wrote:
> On Sat, Jan 18, 2014 at 12:12 AM, Linus Walleij
> wrote:
>> On Fri, Jan 17, 2014 at 8:51 PM, Sherman Yin wrote:
>>
>>> Thanks for the fix, Linus. While we're visiting this config, should we add
>>> "depends on MACH_BCM_MOBILE" as well?
>>
>> No,
On Fri, Jan 17, 2014 at 3:11 PM, John Tobias wrote:
> There's an existing patch for that...
> http://www.spinics.net/lists/arm-kernel/msg296596.html
Ah, I see. Looks like it has yet to be picked up...
>
> On Fri, Jan 17, 2014 at 2:58 PM, Philip Rakity wrote:
>>
>> On Jan 17, 2014, at 7:57 PM,
On Sat, Jan 18, 2014 at 12:12 AM, Linus Walleij
wrote:
> On Fri, Jan 17, 2014 at 8:51 PM, Sherman Yin wrote:
>
>> Thanks for the fix, Linus. While we're visiting this config, should we add
>> "depends on MACH_BCM_MOBILE" as well?
>
> No, it's nice to get the compile coverage.
But maybe you can
On Fri, Jan 17, 2014 at 8:51 PM, Sherman Yin wrote:
> Thanks for the fix, Linus. While we're visiting this config, should we add
> "depends on MACH_BCM_MOBILE" as well?
No, it's nice to get the compile coverage.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe
There's an existing patch for that...
http://www.spinics.net/lists/arm-kernel/msg296596.html
On Fri, Jan 17, 2014 at 2:58 PM, Philip Rakity wrote:
>
> On Jan 17, 2014, at 7:57 PM, Andrew Bresticker wrote:
>
>> sdhci_execute_tuning() takes host->lock without disabling interrupts.
>> Use
On Fri, Jan 17, 2014 at 6:43 PM, Chen-Yu Tsai wrote:
> On Sat, Jan 18, 2014 at 12:47 AM, Arnd Bergmann wrote:
>>> +- NAME_shutdown-gpios : GPIO phandle to shutdown control
>>> + (phandle must be the second)
>>> +- NAME_reset-gpios : GPIO phandle to reset control
>>>
On Fri, Jan 17, 2014 at 2:58 PM, Philip Rakity wrote:
>
> On Jan 17, 2014, at 7:57 PM, Andrew Bresticker wrote:
>
>> sdhci_execute_tuning() takes host->lock without disabling interrupts.
>> Use spin_lock_irq{save,restore} instead so that we avoid taking an
>> interrupt and scheduling while
Continuing on Ivans i2c-qup series.
Changes from v2:
- Removed unused variables and includes
- Corrected read logic in irq handler
- Made the polling loop in qup_i2c_poll_state() less arbitrary
- Only building suspend/resume if CONFIG_PM_SLEEP
Changes from v1:
- Cleaned up device tree
From: "Ivan T. Ivanov"
This bus driver supports the QUP i2c hardware controller in the Qualcomm
MSM SOCs. The Qualcomm Universal Peripheral Engine (QUP) is a general
purpose data path engine with input/output FIFOs and an embedded i2c
mini-core. The driver supports FIFO mode (for low bandwidth
From: "Ivan T. Ivanov"
The Qualcomm Universal Peripherial (QUP) wraps I2C mini-core and
provide input and output FIFO's for it. I2C controller can operate
as master with supported bus speeds of 100Kbps and 400Kbps.
Signed-off-by: Ivan T. Ivanov
[bjorn: reformulated part of binding description
As per linux-next Next/Trees [0], and a recent January MAINTAINERS patch [1]
from David one of the xen development kernel git trees to track is
xen/git.git [2], this tree however gives has undefined references when doing a
fresh clone [shown below], but as expected does work well when only cloning
On Jan 17, 2014, at 7:57 PM, Andrew Bresticker wrote:
> sdhci_execute_tuning() takes host->lock without disabling interrupts.
> Use spin_lock_irq{save,restore} instead so that we avoid taking an
> interrupt and scheduling while holding host->lock.
>
> Signed-off-by: Andrew Bresticker
> ---
>
Some hardware may be broken in interesting and board-specific ways, such
that various bits of functionality don't work. This patch provides a
mechanism for overriding mii registers during init based on the contents of
the device tree data, allowing board-specific fixups without having to
pollute
On Fri, Jan 17, 2014 at 09:34:44PM +0100, Oleg Nesterov wrote:
> On 01/16, Alex Thorlton wrote:
> >
> > static inline int khugepaged_test_exit(struct mm_struct *mm)
> > {
> > - return atomic_read(>mm_users) == 0;
> > + return atomic_read(>mm_users) == 0 ||
> > + (mm->flags &
On Fri, Jan 17, 2014 at 02:51:52PM -0800, H. Peter Anvin wrote:
> Printing a warning is appropriate if we can't actually fix the problem
> in the OS. If we actually make the problem go away then we have just
> done our job and we can be done with it.
And we do make it go away so no warning and a
On Fri, Jan 17, 2014 at 11:54:09AM -0800, Andy Lutomirski wrote:
> Usual nit: please return -EINVAL if unused args are nonzero. This
> makes it possible to extend these APIs in the future.
Got it. Thanks, Andy!
- Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On 01/17/2014 02:50 PM, Borislav Petkov wrote:
> On Fri, Jan 17, 2014 at 11:28:06PM +0100, Pavel Machek wrote:
>> Would it make sense to printk() a warning?
>
> No because people come and start bitching about their dmesg containing
> a warning and whether their hardware is b0rked without even
On Fri, Jan 17, 2014 at 09:09:23PM +0100, Oleg Nesterov wrote:
> On 01/16, Alex Thorlton wrote:
> >
> > + case PR_GET_THP_DISABLE:
> > + error = put_user(test_bit(MMF_THP_DISABLE,
> > +>mm->flags),
> > +(int __user *) arg2);
> > +
On Fri, Jan 17, 2014 at 11:28:06PM +0100, Pavel Machek wrote:
> Would it make sense to printk() a warning?
No because people come and start bitching about their dmesg containing
a warning and whether their hardware is b0rked without even reading the
actual words.
> BIOS is clearly buggy in this
On Fri 2014-01-17 23:02:06, Oleksij Rempel wrote:
> Am 17.01.2014 22:24, schrieb Pavel Machek:
> > On Mon 2013-12-30 19:14:56, Julia Lawall wrote:
> >> Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
> >> used when each argument is an array within a structure that
On Fri, Jan 17, 2014 at 9:53 PM, Russell King - ARM Linux
wrote:
> On Fri, Jan 17, 2014 at 01:42:44PM -0700, Stephen Warren wrote:
>> I believe you want gpio_get_value() to return either the driven or
>> actual pin value where it can on the current HW, but just e.g. hard-code
>> 0 on other HW.
Hi Linus,
Please pull from the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
acpi-3.13-fixup
to receive a last-minute ACPI fix for 3.13 as commit
b40f93bb008ed5d83aa608b21c8c65c5111512e1
Revert "ACPI: Add BayTrail SoC GPIO and LPSS ACPI IDs"
on top
On Tue 2014-01-14 17:27:23, Borislav Petkov wrote:
> From: Borislav Petkov
>
> This adds the workaround for erratum 793 as a precaution in case not
> every BIOS implements it. This addresses CVE-2013-6885.
>
> Signed-off-by: Borislav Petkov
> ---
> arch/x86/kernel/cpu/amd.c | 11 +++
>
> On Fri, Jan 17, 2014 at 14:11 +, Waibel Georg wrote:
> >
> > From cb384950a1153e856ec03109a5156e660a89bf6d Mon Sep 17 00:00:00 2001
> > From: Georg Waibel
> > Date: Fri, 17 Jan 2014 14:51:38 +0100
> > Subject: [PATCH 1/1] iMX gpio: Allow reading back of pin status if
> > configured
> > as
On Fri, Jan 17, 2014 at 02:26:23PM -0500, Joseph Salisbury wrote:
> On 01/17/2014 12:02 PM, Bjorn Helgaas wrote:
> > On Thu, Jan 16, 2014 at 01:14:01PM -0500, Joseph Salisbury wrote:
> >> On 01/16/2014 01:12 PM, Bjorn Helgaas wrote:
> >>> On Thu, Jan 16, 2014 at 10:53 AM, Joseph Salisbury
> >>>
On Fri, Jan 17, 2014 at 6:28 AM, Lothar Waßmann
wrote:
>
> Signed-off-by: Lothar Waßmann
> ---
> .../devicetree/bindings/vendor-prefixes.txt|1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Applied.
Rob
>
> diff --git
On Fri, Jan 17, 2014 at 11:53:07PM +1300, Michael Kerrisk (man-pages) wrote:
> Hi Miklos,
>
> A few comments below, including one piece in the code that really must be
> fixed.
>
> On 01/16/2014 11:54 PM, Miklos Szeredi wrote:
> >> On Wed, Jan 15, 2014 at 7:23 PM, J. Bruce Fields
> >> wrote:
Quoting Maxime Ripard (2014-01-16 09:11:22)
> The A31 has a slightly different PLL6 clock. Add support for this new clock in
> our driver.
>
> Signed-off-by: Maxime Ripard
This looks good to me. I guess it will be going in for 3.15 based on the
comments in the coverletter.
Regards,
Mike
> ---
Am 17.01.2014 22:24, schrieb Pavel Machek:
> On Mon 2013-12-30 19:14:56, Julia Lawall wrote:
>> Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
>> used when each argument is an array within a structure that contains at
>> least two bytes of data beyond the array.
>
> I
On Fri, 17 Jan 2014, Bjorn Helgaas wrote:
On Fri, Jan 17, 2014 at 9:02 AM, Alexander Gordeev wrote:
In case MSI-X and MSI initialization failed the function
irq_set_affinity_hint() is called with uninitialized value
in dev->entry[0].vector. This update fixes the issue.
dev->entry[0].vector
> "nab" == Nicholas A Bellinger writes:
>> That breaks partial completion, though. I'll take a look at Kent's
>> changes...
nab> Ping..? Any updates on a proper bugfix for this..?
I did put your patch in my queue and have been working on a fix for the
partial completion case. The latter
On Fri, Jan 17, 2014 at 1:02 PM, Markus Trippelsdorf
wrote:
> On 2014.01.17 at 11:58 -0800, Alexei Starovoitov wrote:
>> On Fri, Jan 17, 2014 at 9:58 AM, Alexei Starovoitov
>> wrote:
>> > On Fri, Jan 17, 2014 at 5:37 AM, Dorau, Lukasz
>> > wrote:
>> >> Hi
>> >>
>> >> My story is very simply...
On Thu, 16 Jan 2014 14:33:06 +0100 Philipp Hachtmann
wrote:
> This fixes an unused variable warning in nobootmem.c
>
> ...
>
> --- a/mm/nobootmem.c
> +++ b/mm/nobootmem.c
> @@ -116,9 +116,13 @@ static unsigned long __init
> __free_memory_core(phys_addr_t start,
> static unsigned long __init
On Fri, Jan 17, 2014 at 04:03:43PM -0500, J. Bruce Fields wrote:
> - d_splice_alias handles inode == NULL in the same way,
Actually, not exactly; simplifying a bit, in the NULL case they do:
d_splice_alias:
__d_instantiate(dentry, NULL);
On Mon 2013-12-30 19:14:56, Julia Lawall wrote:
> Ether_addr_equal_64bits is more efficient than ether_addr_equal, and can be
> used when each argument is an array within a structure that contains at
> least two bytes of data beyond the array.
I mean, yes, it is probably faster, and yes, most
On Fri, 17 Jan 2014 18:24:28 +0800 Fengguang Wu wrote:
> Hi Davidlohr,
>
> We noticed LTP test failures
>
> ltp.msgget02.1.TFAIL
> ltp.semget02.2.TFAIL
> ltp.semget02.3.TFAIL
>
> and the first bad commit is
>
> commit 5769cf6355d87f63906b3e51887eff7017c39217
> Author:
From: Rik van Riel
The current code in task_numa_placement calculates the difference
between the old and the new value, but also temporarily stores half
of the old value in the per-process variables.
The NUMA balancing code looks at those per-process variables, and
having other tasks
On Fri, 2014-01-17 at 20:21 +, Varun Sethi wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Saturday, January 18, 2014 1:39 AM
> > To: Sethi Varun-B16395
> > Cc: j...@8bytes.org; io...@lists.linux-foundation.org; linux-
> >
From: Rik van Riel
The tracepoint has made it abundantly clear that the naive
implementation of the faults_from code has issues.
Specifically, the garbage collector in some workloads will
access orders of magnitudes more memory than the threads
that do all the active work. This resulted in the
From: Rik van Riel
Use the active_nodes nodemask to make smarter decisions on NUMA migrations.
In order to maximize performance of workloads that do not fit in one NUMA
node, we want to satisfy the following criteria:
1) keep private memory local to each thread
2) avoid excessive NUMA migration
From: Rik van Riel
Being able to see how the active nodemask changes over time, and why,
can be quite useful.
Cc: Peter Zijlstra
Cc: Mel Gorman
Cc: Ingo Molnar
Cc: Chegu Vinod
Signed-off-by: Rik van Riel
---
include/trace/events/sched.h | 34 ++
From: Rik van Riel
The faults_from statistics are used to maintain an active_nodes nodemask
per numa_group. This allows us to be smarter about when to do numa migrations.
Cc: Peter Zijlstra
Cc: Mel Gorman
Cc: Ingo Molnar
Cc: Chegu Vinod
Signed-off-by: Rik van Riel
---
kernel/sched/fair.c
1 - 100 of 1228 matches
Mail list logo
