lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 13 Jan 2009 12:50:29 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Christophe Saout <christophe@...ut.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Bryan Donlan <bdonlan@...il.com>, linux-kernel@...r.kernel.org,
	Nick Piggin <npiggin@...e.de>, linux-mm@...ck.org,
	xen-devel@...ts.xensource.com
Subject: Re: [Xen-devel] Re: OOPS and panic on 2.6.29-rc1 on xen-x86


* Christophe Saout <christophe@...ut.de> wrote:

> Hi Bryan,
> 
> > I've bisected the bug in question, and the faulty commit appears to be:
> > commit e97a630eb0f5b8b380fd67504de6cedebb489003
> > Author: Nick Piggin <npiggin@...e.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@...e.de>
> >     Signed-off-by: Andrew Morton <akpm@...ux-foundation.org>
> >     Signed-off-by: Linus Torvalds <torvalds@...ux-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 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

Powered by Openwall GNU/*/Linux Powered by OpenVZ