linux-kernel - Re: [bug] SLUB + mm/slab.c boot crash in -rc9

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080415084643.GA21586@elte.hu>
Date:	Tue, 15 Apr 2008 10:46:43 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	yhlu.kernel@...il.com
Cc:	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, Christoph Lameter <clameter@....com>,
	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] SLUB + mm/slab.c boot crash in -rc9


* Yinghai Lu <yhlu.kernel.send@...il.com> wrote:

> > why are there no good debug logs possible in this area? To debug 
> > such bugs we'd need an early dump of the precise layout of all 
> > memory maps, what points where, how large it is, where it is 
> > allocated - and then compare it with how the rest of the system is 
> > layed out - looking at possible overlaps or other bugs. This 8-way 
> > box is a pain to debug on, it takes a long time to boot it up, etc. 
> > etc.
> 
> so same config 64 bit with SLUB works and only 32bit is broken? or it 
> 2.6.24 with 32bit + sparse + slub is broken already?

this is a 32-bit-only box.

	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/