On Mon, 2014-01-27 at 01:16 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Drivers should not bind to struct acpi_device objects that
> acpi_bus_trim() has been called for, so make that function
> clear flags.match_driver for those objects.
>
> If that is not done, an ACPI driver
From: Rafael J. Wysocki
Introduce a helper routine for installing acpi_hotplug_notify_cb()
as an ACPI notify handler for the given ACPI namespace node and make
acpi_scan_init_hotplug() use it.
This is to make subsequent changes easier to follow.
Signed-off-by: Rafael J. Wysocki
---
In original bootmem wrapper for memblock, we have limit checking.
Add it to memblock_virt_alloc, to address arm and x86 booting crash.
Signed-off-by: Yinghai Lu
---
mm/memblock.c |3 +++
1 file changed, 3 insertions(+)
Index: linux-2.6/mm/memblock.c
On Tue, 2014-01-28 at 12:20 -0800, Paul E. McKenney wrote:
> On Tue, Jan 28, 2014 at 11:13:12AM -0800, Jason Low wrote:
> > The mutex_can_spin_on_owner() function should also return false if the
> > task needs to be rescheduled to avoid entering the MCS queue when it
> > needs to reschedule.
> >
> inos changing across remounts should be okay,
> right?
Yes that's fine.
-Andi
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Tue, Jan 28, 2014 at 10:53:17PM +0100, Andi Kleen wrote:
> On Tue, Jan 28, 2014 at 04:45:24PM -0500, Tejun Heo wrote:
> > Hello, Andi, Wu.
> >
> > Can you guys please revert 4fd466eb46a6 ("HWPOISON: add memory cgroup
> > filter"), which reaches into cgroup to extract the inode number and
> >
All in kernel users of %n in format strings have now been removed and
the %n directive is ignored. Remove the handling of %n so that it is
treated the same as any other invalid format string directive. Keep a
warning in place to deter new instances of %n in format strings.
Signed-off-by: Ryan
On Tue, Jan 28, 2014 at 04:45:24PM -0500, Tejun Heo wrote:
> Hello, Andi, Wu.
>
> Can you guys please revert 4fd466eb46a6 ("HWPOISON: add memory cgroup
> filter"), which reaches into cgroup to extract the inode number and
> uses that for filtering? Nobody outside cgroup proper should be
Our
used_vectors is a bitmap for vectors that are not tracked in per_cpu
vector_irq.
used_vectors contains information on the first 32 exceptions, the system
vectors.
the IA32_SYSCALL_VECTOR (0x80), and the IRQ_MOVE_CLEANUP_VECTOR (0x20).
assign_irq_vectors() assigns vectors up to
On Tue, Jan 28, 2014 at 1:10 PM, Dave Jones wrote:
>
> This breaks the build for me.
It is my merge (Christoph's ACL changes came in today through the VFS
tree from Al).
I was doing the merges today on my laptop (I had jury duty yesterday
and today), and so I didn't do the allmodconfig build I
On Tue, Jan 28, 2014 at 10:43 AM, Prarit Bhargava wrote:
>
>
> On 01/26/2014 03:50 PM, Yinghai Lu wrote:
>> assign_irq_vector will stop before first_system_vector.
>> also it will not vector that is set in used_vectors.
>>
>> used_vectors is used to track non per_cpu irq_vector in vector_irq.
>>
Hello, Andi, Wu.
Can you guys please revert 4fd466eb46a6 ("HWPOISON: add memory cgroup
filter"), which reaches into cgroup to extract the inode number and
uses that for filtering? Nobody outside cgroup proper should be
reaching into that. In fact, the hard association between vfs objects
and
On 01/28/2014 04:30 PM, Borislav Petkov wrote:
On Tue, Jan 28, 2014 at 04:05:20PM -0500, Boris Ostrovsky wrote:
Yes. This was a bug in our build environment. It is fixed now but I
put this bug back when I was testing your patch.
Right, that was the deal. Oh well, we'd need to verify the
Hello all,
Does anyone using the Marvell SD8797 here?. I tested both the
opensource and the proprietary driver of Marvell for suspend mode (S3)
on iMX6SL board running 3.13 kernel.
In opensource, the driver were able to suspend/resume and able to keep
the IP address and SSID as well, which is
On Tue, Jan 28, 2014 at 04:05:20PM -0500, Boris Ostrovsky wrote:
> Yes. This was a bug in our build environment. It is fixed now but I
> put this bug back when I was testing your patch.
Right, that was the deal. Oh well, we'd need to verify the container
too, I guess:
---
diff --git
On Tuesday 28 January 2014, Kishon Vijay Abraham I wrote:
> > I have a common set of registers, which need to be programmed
> > differently for PCIe and SATA during phy init/exit.
>
> One way is differentiate using different compatible strings fro pcie and sata
> and use of_device_is_compatible
On Tue, 2014-01-28 at 12:23 -0800, Paul E. McKenney wrote:
> On Tue, Jan 28, 2014 at 11:13:13AM -0800, Jason Low wrote:
> > ...
> > if (!owner && (need_resched() || rt_task(task)))
> > - goto slowpath;
> > + break;
> >
> > /*
> >
> Of course, we still need irqs off during ICR writes. I thought Andi was
> just suggesting to replace preempt_disable with get_cpu, maybe to
> document why we are disabling preemption here.
Yes that was my point.
Also with irq-off you of course still always have races against
the NMI-level
On Tue, Jan 28, 2014 at 10:54 AM, Ryan Mallon wrote:
> On 29/01/14 09:51, Kees Cook wrote:
>
>> On Mon, Jan 27, 2014 at 5:02 PM, Ryan Mallon wrote:
>>> On 28/01/14 11:39, Kees Cook wrote:
If arguments are consumed without output when encountering %n, it
could be used to benefit or
On Tue, Jan 28, 2014 at 10:40:16AM -0800, Sage Weil wrote:
> Hi Linus,
>
> Please pull the following Ceph updates from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git
> for-linus
>
> This is a big batch. From Ilya we have:
>
> - rbd support for more than
On Jan 28, 2014, at 5:26 AM, George Spelvin wrote:
>> The third part of the patch further increases the scalablity of an ext4
>> filesystem by having each ext4 fielsystem allocate and use its own private
>> mbcache structure, instead of sharing a single mcache structures across all
>> ext4
On Tue, Jan 28, 2014 at 12:25:15PM -0800, Linus Torvalds wrote:
> On Tue, Jan 28, 2014 at 12:15 PM, Borislav Petkov wrote:
> >
> > Shouldn't we hold that down in the Kconfig help text of DEBUG_INFO?
> > Something like:
> >
> > "You don't need to enable this if you want symbolic names for
On Tue, 28 Jan 2014 23:01:26 +0200 "Kirill A. Shutemov"
wrote:
> On Tue, Jan 28, 2014 at 12:03:01PM -0800, Andrew Morton wrote:
> > On Tue, 28 Jan 2014 11:14:19 + Mark Rutland
> > wrote:
> >
> > > Commit 63d0f0a3c7e1 (mm/readahead.c:do_readhead(): don't check for
> > > ->readpage)
On Tue, 2014-01-28 at 11:13 -0800, Jason Low wrote:
> The mutex_can_spin_on_owner() function should also return false if the
> task needs to be rescheduled to avoid entering the MCS queue when it
> needs to reschedule.
>
> Signed-off-by: Jason Low
Reviewed-by: Davidlohr Bueso
--
To
On Tue, 2014-01-28 at 11:13 -0800, Jason Low wrote:
> v1->v2:
> - Replace the previous patch that limits the # of times a thread can spin with
> !lock->owner with a patch that releases the mutex before holding the
> wait_lock
> in the __mutex_unlock_common_slowpath() function.
> - Add a patch
On Tue, Jan 28, 2014 at 11:13:16AM -0800, Jason Low wrote:
> Before a thread attempts mutex spin on owner, it is first added to a queue
> using an MCS lock so that only 1 thread spins on owner at a time. However,
> when
> the spinner is queued, it is unable to check if it needs to reschedule and
> -Original Message-
> From: Clemens Ladisch [mailto:clem...@ladisch.de]
> Sent: Tuesday, January 28, 2014 3:04 AM
> To: Network Nut
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: WaitForMultipleObjects/etc. In Kernel
>
> Network Nut wrote:
> > 5. I can simulate system-global named
After some idle time I've started running the perf_fuzzer again.
It quickly found this lockup on a core2 system running 3.13 (yes, I should
probably be running 3.14-git but I'd rather wait for rc1 first).
It looks like it's stuck in a lock in generic_exec_single() while
calling
From: "Steven Rostedt (Red Hat)"
The backport of upstream commit 205983c43700ac3 ("sit: allow to use rtnl
ops on fb tunnel") had a dependency on commit 5e6700b3bf98 ("sit: add
support of x-netns"). The dependency was on the way that commit
unregistered the sit devices.
Since the entire commit
From: Willem de Bruijn
[ Upstream commit 9434266f2c645d4fcf62a03a8e36ad8075e37943 ]
Bug: The fallback device is created in sit_init_net and assumed to be
freed in sit_exit_net. First, it is dereferenced in that function, in
sit_destroy_tunnels:
struct net *net =
At Red Hat we base our real-time kernel off of 3.10.27 and do lots of
stress testing on that kernel. This has discovered some bugs that we
can hit with the vanilla 3.10.27 kernel (no -rt patches applied).
I sent out a bug fix that can cause a crash with the current 3.10.27
when you add and then
Commit 7b85b867b9904 "ARM: plat-iop: instantiate GPIO from platform
device" nicely cleaned up the gpio register access for iop, but
forgot one board that directly pokes into the gpio registers
to do a system reset.
That board no longer compiles, and this patch just disables
the code in question
On 01/28/2014 03:52 PM, Borislav Petkov wrote:
On Tue, Jan 28, 2014 at 03:43:57PM -0500, Boris Ostrovsky wrote:
It fixes the case when there is no microcode in initrd but when
microcode is corrupted (as was the case when we were pointing to Intel
binary) we still die. Neither container nor
On Wed, Jan 22, 2014, Sagi Grimberg wrote:
> On 1/22/2014 2:43 AM, Roland Dreier wrote:
>> On Tue, Jan 21, 2014, Or Gerlitz wrote:
>>> Roland, ping! the signature patches were posted > three months ago. We
>>> deserve a response from the maintainer that goes beyond "I need to
>>> think on
On Tue, Jan 28, 2014 at 12:03:01PM -0800, Andrew Morton wrote:
> On Tue, 28 Jan 2014 11:14:19 + Mark Rutland wrote:
>
> > Commit 63d0f0a3c7e1 (mm/readahead.c:do_readhead(): don't check for
> > ->readpage) unintentionally made do_readahead return 0 for all valid
> > files regardless of
Al Viro wrote:
> > ... and then making proc_create() only permit regular files (and complain
> > if the S_IFMT field is not zero)?
>
> We already do: in proc_create_data() we have
> struct proc_dir_entry *pde;
> if ((mode & S_IFMT) == 0)
> mode |= S_IFREG;
>
>
On Tue, 28 Jan 2014 10:59:26 -0800 Sebastian Capella
wrote:
> > Do you have any feedback for me on this?
> >
> > I'm happy do make any changes you think are correct, but I'm unsure if
> > you're asking me for option #3 above. It's quite an intrusive change,
> > and changes old, established
On Tue, Jan 28, 2014 at 11:13:15AM -0800, Jason Low wrote:
> This RFC patch disables preemption between modifying lock->owner and
> locking/unlocking the mutex lock. This prevents situations where the owner
> can preempt between those 2 operations, which causes optimistic spinners to
> be unable
On 29/01/14 09:51, Kees Cook wrote:
> On Mon, Jan 27, 2014 at 5:02 PM, Ryan Mallon wrote:
>> On 28/01/14 11:39, Kees Cook wrote:
>>> If arguments are consumed without output when encountering %n, it
>>> could be used to benefit or improve information leak attacks that were
>>> exposed via a
On Tue, Jan 28, 2014 at 03:43:57PM -0500, Boris Ostrovsky wrote:
> It fixes the case when there is no microcode in initrd but when
> microcode is corrupted (as was the case when we were pointing to Intel
> binary) we still die. Neither container nor ucode_cpio.data is NULL in
> this case.
How is
On Mon, Jan 27, 2014 at 5:02 PM, Ryan Mallon wrote:
> On 28/01/14 11:39, Kees Cook wrote:
>> If arguments are consumed without output when encountering %n, it
>> could be used to benefit or improve information leak attacks that were
>> exposed via a limited size buffer. Since %n is not used by
On Tue, Jan 28, 2014 at 12:25:15PM -0800, Linus Torvalds wrote:
> Probably. And then we should make sure that allyesconfig/allmodconfig
> don't pick it.
I'd need to think about that a bit longer as scripts/kconfig/conf.c goes
and sets those. Unless someone has a better idea...
> There *are*
The merge between 2b7f65b11d87f "mmp_pdma: Style neatening" and
8010dad55a0ab0 "dma: add dma_get_any_slave_channel(), for use in of_xlate()"
caused a build error by leaving obsolete code in place:
mmp_pdma.c: In function 'mmp_pdma_dma_xlate':
mmp_pdma.c:909:31: error: 'candidate' undeclared
On 01/28/2014 11:24 AM, Borislav Petkov wrote:
On Thu, Jan 23, 2014 at 02:41:59PM -0500, Boris Ostrovsky wrote:
32-bit only.
Ok, I think I know what happens. Can you try this one (I missed doing
this on 32-bit and 64-bit does it, which would explain why it didn't
explode there):
---
diff
On 01/28/2014 12:28 PM, Richard Weinberger wrote:
> Am 28.01.2014 21:25, schrieb Linus Torvalds:
>> On Tue, Jan 28, 2014 at 12:15 PM, Borislav Petkov wrote:
>>>
>>> Shouldn't we hold that down in the Kconfig help text of DEBUG_INFO?
>>> Something like:
>>>
>>> "You don't need to enable this if
On 01/28/2014 02:38 PM, Konrad Rzeszutek Wilk wrote:
On Tue, Jan 28, 2014 at 06:43:32PM +0100, Roger Pau Monne wrote:
blkback bug fixes for memory leaks (patches 1 and 2) and a race
(patch 3).
They all look OK to me. I've stuck them in my 'stable/for-jens-3.14'
branch and are testing them now
Am 28.01.2014 21:25, schrieb Linus Torvalds:
> On Tue, Jan 28, 2014 at 12:15 PM, Borislav Petkov wrote:
>>
>> Shouldn't we hold that down in the Kconfig help text of DEBUG_INFO?
>> Something like:
>>
>> "You don't need to enable this if you want symbolic names for kernel
>> objects. Enable
On Tue, Jan 28, 2014 at 08:20:12PM +, David Howells wrote:
> Linus Torvalds wrote:
>
> > > - p = proc_create("cells", 0, proc_afs, _proc_cells_fops);
> > > + p = proc_create("cells", S_IFREG | S_IRUGO | S_IWUSR, proc_afs,
> > > _proc_cells_fops);
> > > - p =
From: Pali Rohár
Both proc files are writeable and used for configuring cells. But
there is missing correct mode flag for writeable files. Without
this patch both proc files are read only.
Signed-off-by: Pali Rohár
Signed-off-by: David Howells
---
fs/afs/proc.c |4 ++--
1 file changed,
On Tue, Jan 28, 2014 at 12:15 PM, Borislav Petkov wrote:
>
> Shouldn't we hold that down in the Kconfig help text of DEBUG_INFO?
> Something like:
>
> "You don't need to enable this if you want symbolic names for kernel
> objects. Enable CONFIG_KALLSYMS instead."
Probably. And then we should
On Tue, Jan 28, 2014 at 12:23:34PM -0800, Paul E. McKenney wrote:
> On Tue, Jan 28, 2014 at 11:13:13AM -0800, Jason Low wrote:
> > The mutex->spin_mlock was introduced in order to ensure that only 1 thread
> > spins for lock acquisition at a time to reduce cache line contention. When
> >
On Tue, Jan 28, 2014 at 11:13:13AM -0800, Jason Low wrote:
> The mutex->spin_mlock was introduced in order to ensure that only 1 thread
> spins for lock acquisition at a time to reduce cache line contention. When
> lock->owner is NULL and the lock->count is still not 1, the spinner(s) will
>
On 01/28/2014 01:12 PM, Geert Uytterhoeven wrote:
> drivers/char/ipmi/ipmi_si_intf.c: In function 'ipmi_parisc_probe':
> drivers/char/ipmi/ipmi_si_intf.c:2752:2: error: 'rv' undeclared (first use in
> this function)
> drivers/char/ipmi/ipmi_si_intf.c:2752:2: note: each undeclared identifier is
>
On Tue, Jan 28, 2014 at 11:13:12AM -0800, Jason Low wrote:
> The mutex_can_spin_on_owner() function should also return false if the
> task needs to be rescheduled to avoid entering the MCS queue when it
> needs to reschedule.
>
> Signed-off-by: Jason Low
Reviewed-by: Paul E. McKenney
But I
Linus Torvalds wrote:
> > - p = proc_create("cells", 0, proc_afs, _proc_cells_fops);
> > + p = proc_create("cells", S_IFREG | S_IRUGO | S_IWUSR, proc_afs,
> > _proc_cells_fops);
> > - p = proc_create("rootcell", 0, proc_afs, _proc_rootcell_fops);
> > + p =
On Tue, 2014-01-28 at 16:03 +0100, Olaf Hering wrote:
>
> d084775738b746648d4102337163a04534a02982 is the first bad commit
> commit d084775738b746648d4102337163a04534a02982
> Author: Alistair Popple
> Date: Mon Dec 9 18:17:03 2013 +1100
>
> powerpc/iommu: Update the generic code to use
On Tue, Jan 28, 2014 at 12:17 PM, Linus Torvalds
wrote:
> On Tue, Jan 28, 2014 at 10:22 AM, Russell King - ARM Linux
> wrote:
>>
>> Hence, having ARCH_LOW_ADDRESS_LIMIT set to 4GB-1 by default seems to be
>> completely rediculous - and presumably this also fails on x86_32 if it
>> returns memory
Hi all,
Sorry, for the invalid mail & patch format - have no way to send it properly
now.
Suppose there is another way to fix this issue (more generic)
- Correct memblock_virt_allocX() API to limit allocations below
memblock.current_limit
(patch attached).
Then the code behavior will become
On Tue, Jan 28, 2014 at 10:22 AM, Russell King - ARM Linux
wrote:
>
> Hence, having ARCH_LOW_ADDRESS_LIMIT set to 4GB-1 by default seems to be
> completely rediculous - and presumably this also fails on x86_32 if it
> returns memory up at 4GB.
Agreed. That looks broken even on x86-32. The low
On Tue, Jan 28, 2014 at 11:55 AM, Yinghai Lu wrote:
> but looks like memblock_virt_alloc_low is not the same as alloc_bootmem_low
> yet.
>
The memblock_virt_alloc missed limit checking.
Please check attached patch.
Thanks
Yinghai
Subject: [PATCH] memblock: Add limit checking to
From: Heinrich Schuchardt
revised patch
p is freed if NULL.
p is leaked if second calloc fails.
Signed-off-by: Heinrich Schuchardt
---
drivers/staging/usbip/userspace/libsrc/names.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
From: David Howells
Date: Tue, 28 Jan 2014 20:11:17 +
> Do you prefer git pulls or patches posting for networking stuff?
Both ways work equally for me, to be honest.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Tue, Jan 28, 2014 at 12:07:26PM -0800, Linus Torvalds wrote:
> On Tue, Jan 28, 2014 at 11:48 AM, Ingo Molnar wrote:
> >
> > I really meant it when I said I build without debuginfo! :)
>
> Ok, but so what?
>
> As mentioned, nobody sane should build with DEBUG_INFO.
Shouldn't we hold that
Hi Dave,
Do you prefer git pulls or patches posting for networking stuff?
David
--
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 http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On Tue, Jan 28, 2014 at 11:48 AM, Ingo Molnar wrote:
>
> I really meant it when I said I build without debuginfo! :)
Ok, but so what?
As mentioned, nobody sane should build with DEBUG_INFO. But a normal
vmlinux file has the symbol information even without it.
> So, when I build a kernel, such
On Tue, 28 Jan 2014 11:14:19 + Mark Rutland wrote:
> Commit 63d0f0a3c7e1 (mm/readahead.c:do_readhead(): don't check for
> ->readpage) unintentionally made do_readahead return 0 for all valid
> files regardless of whether readahead was supported, rather than the
> expected -EINVAL. This gets
On Tue, Jan 28, 2014 at 11:47 AM, Russell King - ARM Linux
wrote:
> On Tue, Jan 28, 2014 at 11:43:02AM -0800, Yinghai Lu wrote:
>> On Tue, Jan 28, 2014 at 9:18 AM, Russell King - ARM Linux
>> wrote:
>> > On Tue, Jan 28, 2014 at 09:12:27AM -0800, Yinghai Lu wrote:
>> >> On Tue, Jan 28, 2014 at
On Tue, 28 Jan 2014, Julien Grall wrote:
> Event channels driver needs to be initialized very early. Until now, Xen
> initialization was done after all CPUs was bring up.
>
> We can safely move the initialization to an early initcall.
>
> Also use a cpu notifier to:
> - Register the VCPU
> This 444 should have been octal.
Right, my fault. We are not using the sysfs interface for module
parameters, so I didn't notice.
> Signed-off-by: Joe Perches
Acked-by: Alessandro Rubini
thanks
/alessandro, with two other minor fmc fixes to submit soon
--
To unsubscribe from this list:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
> On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
> > > +
> > > +Clients must use the format described in the dma.txt file, using a three
> > > cell
> > > +specifier for each channel.
> > > +
> > > +The three cells in
On Thu, 23 Jan 2014, Benjamin Tissoires wrote:
> This is a Win7 device which does not work correctly with the default
> settings (not the previous default BT).
> However, the quirk ALWAYS_TRUE makes it working like a charm.
>
> Signed-off-by: Benjamin Tissoires
> ---
>
> Hi Jiri,
>
> well,
* Linus Torvalds wrote:
> On Tue, Jan 28, 2014 at 9:05 AM, Ingo Molnar wrote:
> >
> > Well, I often use the hex numbers to look them up and disassemble them
> > in a vmlinux via gdb and 'list *0x1234123412341234' - where the
> > vmlinux has no debuginfo. (Debuginfo takes longer to build so I
>
On Tue, Jan 28, 2014 at 11:43:02AM -0800, Yinghai Lu wrote:
> On Tue, Jan 28, 2014 at 9:18 AM, Russell King - ARM Linux
> wrote:
> > On Tue, Jan 28, 2014 at 09:12:27AM -0800, Yinghai Lu wrote:
> >> On Tue, Jan 28, 2014 at 7:30 AM, Kevin Hilman wrote:
> >> > Like Olof, I noticed multiple boot
On Tue, Jan 28, 2014 at 10:05:35AM +0100, Lars-Peter Clausen wrote:
> On 01/28/2014 07:27 AM, Andy Gross wrote:
> > Add device tree binding support for the QCOM BAM DMA driver.
> >
> > Signed-off-by: Andy Gross
> > ---
> > .../devicetree/bindings/dma/qcom_bam_dma.txt | 52
> >
On Tue, Jan 28, 2014 at 9:18 AM, Russell King - ARM Linux
wrote:
> On Tue, Jan 28, 2014 at 09:12:27AM -0800, Yinghai Lu wrote:
>> On Tue, Jan 28, 2014 at 7:30 AM, Kevin Hilman wrote:
>> > Like Olof, I noticed multiple boot failures on various ARM boards.
>> > I've confirmed that reverting the
On Tue, Jan 28, 2014 at 06:17:00PM +0100, Daniel Vetter wrote:
> On Wed, Jan 8, 2014 at 7:43 PM, Ville Syrjälä
> wrote:
> >
> > The log looks fairly clear to me:
> >
> > 1. initially panel fitter is enabled on pipe B, and pipe B is outputting
> >to LVDS and VGA. Border is enabled.
> > 2. pipe
On Tue, Jan 28, 2014 at 06:43:32PM +0100, Roger Pau Monne wrote:
> blkback bug fixes for memory leaks (patches 1 and 2) and a race
> (patch 3).
They all look OK to me. I've stuck them in my 'stable/for-jens-3.14'
branch and are testing them now (hadn't pushed it yet).
Matt and Matt,
Could you
On Tue, Jan 28, 2014 at 11:40:57AM -0700, Bjorn Helgaas wrote:
> On Mon, Jan 27, 2014 at 6:30 PM, David Cohen
> wrote:
> > Hi Bjorn,
> >
> > On Mon, Jan 27, 2014 at 05:52:30PM -0700, Bjorn Helgaas wrote:
> >> On Mon, Dec 16, 2013 at 1:07 PM, David Cohen
> >> wrote:
> >> > This code was partially
On Sat, Jan 25, 2014 at 4:23 AM, Oleg Drokin wrote:
> On Jan 24, 2014, at 3:55 AM, Geert Uytterhoeven wrote:
>> On Fri, Jan 24, 2014 at 6:51 AM, Oleg Drokin wrote:
+STAGING - LUSTRE
+M: Andreas Dilger
+M: Oleg Drokin
+M: Peng Tao .
+L: hpdd-discuss
+S:
On Tue, Jan 28, 2014 at 11:25:12AM -0800, tip-bot for Peter Zijlstra wrote:
> Commit-ID: 673c36745c9f3100672853840b27e27638435e74
> Gitweb: http://git.kernel.org/tip/673c36745c9f3100672853840b27e27638435e74
> Author: Peter Zijlstra
> AuthorDate: Tue, 28 Jan 2014 15:12:36 +0100
>
Commit-ID: 52bf84aa206cd2c2516dfa3e03b578edf8a3242f
Gitweb: http://git.kernel.org/tip/52bf84aa206cd2c2516dfa3e03b578edf8a3242f
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:40 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:17:04 +0100
sched/numa, mm: Remove
Commit-ID: aff7385b5a16bca6b8d9243f01a9ea5a5b411e1d
Gitweb: http://git.kernel.org/tip/aff7385b5a16bca6b8d9243f01a9ea5a5b411e1d
Author: Waiman Long
AuthorDate: Tue, 21 Jan 2014 15:35:53 -0800
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:13:26 +0100
locking/mutexes/mcs:
Commit-ID: ff1df896aef8e0ec1556a5c44f424bd45bfa2cbe
Gitweb: http://git.kernel.org/tip/ff1df896aef8e0ec1556a5c44f424bd45bfa2cbe
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:41 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:17:05 +0100
sched/numa: Rename
Commit-ID: be1e4e760d940c14d119bffef5eb007dfdf29046
Gitweb: http://git.kernel.org/tip/be1e4e760d940c14d119bffef5eb007dfdf29046
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:48 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 15:03:21 +0100
sched/numa: Turn some
Commit-ID: 58b46da336a9312b2e21bb576d1c2c484dbf6257
Gitweb: http://git.kernel.org/tip/58b46da336a9312b2e21bb576d1c2c484dbf6257
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:47 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 15:03:19 +0100
sched/numa: Rename
Commit-ID: 673c36745c9f3100672853840b27e27638435e74
Gitweb: http://git.kernel.org/tip/673c36745c9f3100672853840b27e27638435e74
Author: Peter Zijlstra
AuthorDate: Tue, 28 Jan 2014 15:12:36 +0100
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 15:27:36 +0100
x86, um: Add generic
Commit-ID: 7e2703e6099609adc93679c4d45cd6247f565971
Gitweb: http://git.kernel.org/tip/7e2703e6099609adc93679c4d45cd6247f565971
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:45 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 15:03:10 +0100
sched/numa: Normalize
Commit-ID: e207552e64ea053a33e856828ad7915484911d06
Gitweb: http://git.kernel.org/tip/e207552e64ea053a33e856828ad7915484911d06
Author: Will Deacon
AuthorDate: Tue, 21 Jan 2014 15:36:10 -0800
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:13:28 +0100
locking/mcs: Allow
Commit-ID: e72246748ff006ab928bc774e276e6ef5542f9c5
Gitweb: http://git.kernel.org/tip/e72246748ff006ab928bc774e276e6ef5542f9c5
Author: Tim Chen
AuthorDate: Tue, 21 Jan 2014 15:36:00 -0800
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:13:27 +0100
locking/mutexes/mcs:
Commit-ID: 50ec8a401fed6d246ab65e6011d61ac91c34af70
Gitweb: http://git.kernel.org/tip/50ec8a401fed6d246ab65e6011d61ac91c34af70
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:42 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:17:05 +0100
sched/numa: Track from
Commit-ID: 10f39042711ba21773763f267b4943a2c66c8bef
Gitweb: http://git.kernel.org/tip/10f39042711ba21773763f267b4943a2c66c8bef
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:44 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:17:07 +0100
sched/numa, mm: Use
Commit-ID: 20e07dea286a90f096a779706861472d296397c6
Gitweb: http://git.kernel.org/tip/20e07dea286a90f096a779706861472d296397c6
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:43 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:17:06 +0100
sched/numa: Build per
Commit-ID: 35664fd41e1c8cc4f0b89f6a51db5af39ba50640
Gitweb: http://git.kernel.org/tip/35664fd41e1c8cc4f0b89f6a51db5af39ba50640
Author: Rik van Riel
AuthorDate: Mon, 27 Jan 2014 17:03:46 -0500
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 15:03:17 +0100
sched/numa: Do statistics
Jean-Francois Moine wrote on Tue [2014-Jan-28 18:12:18 +0100]:
> On Thu, 23 Jan 2014 17:29:07 -0600
> Darren Etheridge wrote:
>
> > > @@ -896,9 +897,9 @@ tda998x_encoder_mode_set(struct drm_encoder *encoder,
> > >* TDA19988 requires high-active sync at input stage,
> > >* so invert
On Tue, 28 Jan 2014, George Spelvin wrote:
I'm trying it now. But it takes a while for me to reproduce, and even
longer to be sure the problem has gone away. So anything you hear from
me within a week will be bad news.
Well, it's been a week, and: good news!
I'd still wish for some review
Commit-ID: 5faeb8adb956a5ad6579c4e309e8689943ad8294
Gitweb: http://git.kernel.org/tip/5faeb8adb956a5ad6579c4e309e8689943ad8294
Author: Jason Low
AuthorDate: Tue, 21 Jan 2014 15:36:05 -0800
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:13:28 +0100
locking/mcs: Micro-optimize
Commit-ID: a57beec5d427086cdc8d75fd51164577193fa7f4
Gitweb: http://git.kernel.org/tip/a57beec5d427086cdc8d75fd51164577193fa7f4
Author: Peter Zijlstra
AuthorDate: Mon, 27 Jan 2014 11:54:13 +0100
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:08:41 +0100
sched: Make
Commit-ID: 712e5e34aef449ab680b35c0d9016f59b0a4494c
Gitweb: http://git.kernel.org/tip/712e5e34aef449ab680b35c0d9016f59b0a4494c
Author: Dario Faggioli
AuthorDate: Mon, 27 Jan 2014 12:20:15 +0100
Committer: Ingo Molnar
CommitDate: Tue, 28 Jan 2014 13:08:40 +0100
sched/deadline: Add
When running workloads that have high contention in mutexes on an 8 socket
machine, mutex spinners would often spin for a long time with no lock owner.
The main reason why this is occuring is in __mutex_unlock_common_slowpath(),
if __mutex_slowpath_needs_to_unlock(), then the owner needs to
v1->v2:
- Replace the previous patch that limits the # of times a thread can spin with
!lock->owner with a patch that releases the mutex before holding the wait_lock
in the __mutex_unlock_common_slowpath() function.
- Add a patch which allows a thread to attempt 1 mutex_spin_on_owner() without
201 - 300 of 1194 matches
Mail list logo
