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
| ||
|
Date: Mon, 29 Oct 2007 12:51:49 -0700 (PDT) From: Christoph Lameter <clameter@....com> To: Linus Torvalds <torvalds@...ux-foundation.org> cc: Greg KH <greg@...ah.com>, Dave Jones <davej@...hat.com>, Linux Kernel <linux-kernel@...r.kernel.org>, Martin Ebourne <fedora@...urne.me.uk>, Zou Nan hai <nanhai.zou@...el.com>, Suresh Siddha <suresh.b.siddha@...el.com>, Andi Kleen <ak@...e.de>, stable@...nel.org, Andrew Morton <akpm@...ux-foundation.org>, Andy Whitcroft <apw@...dowen.org>, Mel Gorman <mel@....ul.ie> Subject: Re: [stable] 2.6.23 boot failures on x86-64. On Mon, 29 Oct 2007, Linus Torvalds wrote: > We've had some changes since 2.6.23, and afaik, the > "alloc_bootmem_high_node()" code is alreadt effectively dead there. It's > only called if CONFIG_SPARSEMEM_VMEMMAP is *not* enabled, and I *think* we > enable it by force on x86-64 these days. CONFIG_SPARSEMEM_VMEMMAP was introduced in 2.6.24-rc1. If I read this Kconfig.x86_64 correctly then it seems that DISCONTIG is still the default. Andy? config ARCH_DISCONTIGMEM_ENABLE bool depends on NUMA default y config ARCH_DISCONTIGMEM_DEFAULT def_bool y depends on NUMA config ARCH_SPARSEMEM_ENABLE def_bool y depends on (NUMA || EXPERIMENTAL) select SPARSEMEM_VMEMMAP_ENABLE config ARCH_MEMORY_PROBE def_bool y depends on MEMORY_HOTPLUG config ARCH_FLATMEM_ENABLE def_bool y depends on !NUMA - 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