linux-kernel - Re: [bug] mm/slab.c boot crash in -git, "kernel BUG at mm/slab.c:2103!"

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]

Message-ID: <20080415054939.GB7420@elte.hu>
Date:	Tue, 15 Apr 2008 07:49:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Christoph Lameter <clameter@....com>
Cc:	travis@....com, Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@....ul.ie>,
	Nick Piggin <npiggin@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [bug] mm/slab.c boot crash in -git, "kernel BUG at
	mm/slab.c:2103!"


* Christoph Lameter <clameter@....com> wrote:

> On Fri, 11 Apr 2008, Pekka Enberg wrote:
> 
> > slab bug and I don't see any recent changes to the page allocator
> > either that would explain this.
> 
> I also have an internal report that x86-git causes boot to fail with 
> an 8p if one starts with a x86_64 config file and then converts to 
> x86_32. Somehow the NR_CPUS is set to 255 in that case. Could this 
> exhaust memory? I guess the per cpu cleanup work may figure in that 
> area. Mike?

how about reading my bugreport that you replied to:

   http://lkml.org/lkml/2008/4/11/34

It gives an answer to your question, trivially so. It includes an easy 
link to the very config that failed:

   http://redhat.com/~mingo/misc/config-Thu_Apr_10_10_41_16_CEST_2008.bad

which would tell you:

   CONFIG_NR_CPUS=8

so no, it's not 255 CPUs exhausing RAM ...

	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/