Ingo,
I wrote a test that triggers the bug, and tested this patch which seems
to fix it as well.
Please pull the latest tip/perf/urgent tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/urgent
Head SHA1: 85f2a2ef1d0ab99523e0b947a2b723
The patch titled
Subject: trace/events/kmem: don't call page_to_pfn() if page is NULL
has been added to the -mm tree. Its filename is
trace-events-kmem-dont-call-page_to_pfn-if-page-is-null.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b)
Timur Tabi wrote:
> equivalent to commit 6269f2584a359766f53005c676daff8aee60cbed upstream
>
> The Freescale P1022 has a unique pin muxing "feature" where the DIU video
> controller's video signals are muxed with 24 of the local bus address signals.
> When the DIU is enabled, the bulk of the local
On Wed, 2012-09-19 at 22:02 +0200, Bjørn Mork wrote:
> The three Pantech devices UML190 (106c:3716), UML290 (106c:3718) and
> P4200 (106c:3721) all use the same subclasses to identify vendor
> specific functions. Replace the existing device specific entries
> with generic vendor matching, adding s
From: Christian König
Only increase the higher 32bits if we really detect a wrap around.
v2: instead of increasing the higher 32bits just use the higher
32bits from the last emitted fence.
v3: also use last emitted fence value as upper limit.
The intention of this patch is to make fences as
On Thu, 2012-09-20 at 15:28 +0900, Minchan Kim wrote:
> On Thu, Sep 20, 2012 at 02:04:47PM +0800, Wen Congyang wrote:
> > When allocating memory fails, page is NULL. page_to_pfn() will
> > cause the kernel panicked if we don't use sparsemem vmemmap.
> >
> > Signed-off-by: Wen Congyang
>
> Nice c
On Thursday 20 September 2012 16:26:18 Ming Lei wrote:
> On Thu, Sep 20, 2012 at 3:29 PM, Oliver Neukum wrote:
> > On Thursday 20 September 2012 13:28:51 Ming Lei wrote:
> >> If one usb interface driver returns failure from its
> >> suspend(auto) callback inside usb_suspend_both, its
> >> resume()
On Thu, Sep 20, 2012 at 3:29 PM, Oliver Neukum wrote:
> On Thursday 20 September 2012 13:28:51 Ming Lei wrote:
>> If one usb interface driver returns failure from its
>> suspend(auto) callback inside usb_suspend_both, its
>> resume() callback should be called to recover its
>> working state.
>
> N
On 09/20/2012 04:49 PM, Chris Wilson wrote:
On Thu, 20 Sep 2012 15:10:39 +0900, Joonyoung Shim
wrote:
On 09/20/2012 02:38 PM, Rob Clark wrote:
On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim wrote:
On 09/17/2012 06:38 PM, Chris Wilson wrote:
As during the plane cleanup, we wish to disable
On Thu, 20 Sep 2012 15:10:39 +0900, Joonyoung Shim
wrote:
> On 09/20/2012 02:38 PM, Rob Clark wrote:
> > On Wed, Sep 19, 2012 at 9:52 PM, Joonyoung Shim
> > wrote:
> >> On 09/17/2012 06:38 PM, Chris Wilson wrote:
> >>> As during the plane cleanup, we wish to disable the hardware and
> >>> so ma
On Thursday 20 September 2012 13:28:51 Ming Lei wrote:
> If one usb interface driver returns failure from its
> suspend(auto) callback inside usb_suspend_both, its
> resume() callback should be called to recover its
> working state.
NO!
The interface is defined so that if you fail, this is your
p
11 matches
Mail list logo