linux-kernel - Re: [PATCH RFC] x86: add brk allocation for very, very early allocations

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]

Message-ID: <49A854ED.7020401@goop.org>
Date:	Fri, 27 Feb 2009 13:02:37 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] x86: add brk allocation for very, very early allocations

Yinghai Lu wrote:
> it seems reserve _brk_end is some late?
>
> init_memory_mapping(0,...) could get some for direct mapping page table. and it could start from _end...
>   

Ah, thanks!  I was confused by the use of reserve_early() in 
initmem_init(), but they're OK because they allocate out of the e820 map 
at that point (and init_memory_mapping() reserves everything it allocates).

I'll give it a whirl.

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