From: Ingo Molnar <mingo@elte.hu>
To: Christophe Saout <christophe@saout.de>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Bryan Donlan <bdonlan@gmail.com>,
linux-kernel@vger.kernel.org, Nick Piggin <npiggin@suse.de>,
linux-mm@kvack.org, xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: OOPS and panic on 2.6.29-rc1 on xen-x86
Date: Tue, 13 Jan 2009 12:50:29 +0100 [thread overview]
Message-ID: <20090113115029.GA12055@elte.hu> (raw)
In-Reply-To: <1231838731.4823.2.camel@leto.intern.saout.de>
* Christophe Saout <christophe@saout.de> wrote:
> Hi Bryan,
>
> > I've bisected the bug in question, and the faulty commit appears to be:
> > commit e97a630eb0f5b8b380fd67504de6cedebb489003
> > Author: Nick Piggin <npiggin@suse.de>
> > Date: Tue Jan 6 14:39:19 2009 -0800
> >
> > mm: vmalloc use mutex for purge
> >
> > The vmalloc purge lock can be a mutex so we can sleep while a purge is
> > going on (purge involves a global kernel TLB invalidate, so it can take
> > quite a while).
> >
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> >
> > The bug is easily reproducable by a kernel build on -j4 - it will
> > generally OOPS and panic before the build completes.
> > Also, I've tested it with ext3, and it still occurs, so it seems
> > unrelated to btrfs at least :)
>
> Nice!
>
> Reverting this also fixes the BUG() I was seeing when testing the Dom0
> patches on 2.6.29-rc1+tip. It just ran stable for an hour compiling
> gimp and playing music on my notebook (and then I had to leave).
okay - i've reverted it in tip/master so that testing can continue - but
the upstream fix (or revert) should be done via the MM folks.
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-01-13 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090112172613.GA8746@shion.is.fushizen.net>
2009-01-13 4:54 ` OOPS and panic on 2.6.29-rc1 on xen-x86 Bryan Donlan
2009-01-13 9:25 ` [Xen-devel] " Christophe Saout
2009-01-13 11:50 ` Ingo Molnar [this message]
2009-01-14 2:59 ` Nick Piggin
2009-01-14 21:05 ` Bryan Donlan
2009-01-15 0:19 ` Bryan Donlan
2009-01-15 16:36 ` Christophe Saout
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090113115029.GA12055@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=bdonlan@gmail.com \
--cc=christophe@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).