linux-kernel - Re: [PATCH 0/2] panics booting NUMA SPARSEMEM on x86

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] [day] [month] [year] [list]

Message-ID: <20080520120855.GA10080@elte.hu>
Date:	Tue, 20 May 2008 14:08:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andy Whitcroft <apw@...dowen.org>
Cc:	Mel Gorman <mel@....ul.ie>, Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Yinghai Lu <yhlu.kernel@...il.com>
Subject: Re: [PATCH 0/2] panics booting NUMA SPARSEMEM on x86_32 NUMA


* Andy Whitcroft <apw@...dowen.org> wrote:

> We have been seeing panics booting NUMA SPARSEMEM kernels on x86_32 
> hardware, while trying to allocate node local memory in early boot. 
> These are caused by a miss-allocation of the node pgdat structures 
> when numa remap is disabled.
> 
> Following this email are two patches, the first reenables numa remap 
> for SPARSEMEM as the underlying bug has now been fixed.  The second 
> hardens the pgdat allocation in the face of there being no numa remap 
> for a particular node (which may still occur).

applied to -tip, thanks Andy.

	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/