linux-kernel - Config NO_BOOTMEM breaks my amd64 box

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

Message-ID: <alpine.LRH.2.00.1003311539490.23281@tundra.namei.org>
Date:	Wed, 31 Mar 2010 15:49:06 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	linux-kernel@...r.kernel.org, airlied@...ux.ie
Subject: Config NO_BOOTMEM breaks my amd64 box

Please make NO_BOOTMEM default to n, at least for amd64, where I've found 
that it leads to all kinds of strange, undebuggable boot hangs and errors 
(with relatively current Fedora development userland).

Also, the help text for the item makes little sense to a non-expert in 
this area:

" ---help---
          Use early_res directly instead of bootmem before slab is ready.
                - allocator (buddy) [generic]
                - early allocator (bootmem) [generic]
                - very early allocator (reserve_early*()) [x86]
                - very very early allocator (early brk model) [x86]
          So reduce one layer between early allocator to final allocator."

I had no idea what all this meant, so trusted the default=y and then spent 
several hours wondering why everything was breaking, and would likley not 
have figured it out in linear time without a suggestion from Dave Airlie.

- James
-- 
James Morris
<jmorris@...ei.org>
--
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/