[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1004101427090.3618@i5.linux-foundation.org>
Date: Sat, 10 Apr 2010 14:30:49 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Borislav Petkov <bp@...en8.de>
cc: Johannes Weiner <hannes@...xchg.org>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan.kim@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>,
Nick Piggin <npiggin@...e.de>,
Andrea Arcangeli <aarcange@...hat.com>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
sgunderson@...foot.com
Subject: Re: [PATCH -v2] rmap: make anon_vma_prepare link in all the anon_vmas
of a mergeable VMA
On Sat, 10 Apr 2010, Borislav Petkov wrote:
>
> Damn, nope, still no joy :(. It looked like it was fixed but one of the
> test was to hibernate right after the 3 kvm guests were shut down and I
> guess the mem freeing pattern kinda hits it where it most hurts.
Damn, I really hoped that was it. Three independent bugs found and fixed,
and still no joy? Oh well.
> By the way, do we want to create a new thread - the mailchain is off the
> screen limits of my netbook :)
I prefer to keep it in one thread so that they all show up together if I
need to, but feel free to start a new one. Not a biggie.
> [ 647.492781] BUG: unable to handle kernel NULL pointer dereference at (null)
> [ 647.493001] IP: [<ffffffff810c60a0>] page_referenced+0xee/0x1dc
Well, it sure is consistent. I'll start to think about what else could go
wrong..
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists