linux-kernel - Re: Latest brk patchset

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:	Sat, 14 Mar 2009 23:25:56 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Latest brk patchset

Jeremy Fitzhardinge wrote:
> Yinghai Lu wrote:
>> 64 bit does not has this problem.
>> 32 bit we already removed bootmem there, that is not needed.
>> ALLOCATOR_SLOP is needed...
>>
>> + *     (KERNEL_IMAGE_SIZE/4096) / 1024 pages (worst case, non PAE)
>> + *     (KERNEL_IMAGE_SIZE/4096) / 512 + 4 pages (worst case for PAE)
> 
> Yes, ALLOCATOR_SLOP is a different matter; its the amount of space the
> boot allocator needs for its own space management.  But 1) doesn't
> 64-bit need this too (since its the same code), and 2) couldn't it be
> allocated out of brk?

need to double check if we really need allocator_slop.
we only need to make sure init_memory_mapping() could get ram spaces that is already mapped for extra page tables.

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