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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 15 Apr 2008 13:03:49 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Ingo Molnar <mingo@...e.hu>
cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@....ul.ie>,
	Nick Piggin <npiggin@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Yinghai.Lu@....com,
	apw@...dowen.org,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [bug] SLUB + mm/slab.c boot crash in -rc9

On Tue, 15 Apr 2008, Ingo Molnar wrote:

> Pretty please, could you pay more than cursory attention to this bug i 
> already spent two full days on and which is blocking the v2.6.25 
> release?

Yeah trying to get to understand how exactly sparsemem works and how the 
32 bit highmem stuff interacts with it... Sorry not code that I am an 
expert in nor the platform that I am familiar with. Code mods there 
required heavy review from multiple parties with expertise in various 
subjects.

> I'm just guessing my way around, but right now my impression is that the 
> current early memory setup code is unrobust, over-complex, occasionally 
> butt-ugly to read code in high need of cleanups, simplifications and 
> debug facilities, visibly plagued by hit-and-run changes with frequent 
> typos and everything else you normally dont want to see in the core 
> kernel. (Did i get your attention now? ;-)

I thought the NR_SECTIONS stuff would trigger some memories. Adding apw 
who seemed to be most familiar with the material in the past 
(AFAICT NODE_NOT_IN_PAGE_FLAGS is there for IBM NUMAQ etc) and Kame-san.

Andy, Kame-san could you have a look at the sparsemem config issue with 
32 bit !PAE? This is SPARSEMEM_STATIC.

--
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/