linux-kernel - Re: brk patches..

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: <49A8F319.3030802@goop.org>
Date:	Sat, 28 Feb 2009 00:17:29 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: brk patches..

Yinghai Lu wrote:
> Yinghai Lu wrote:
>   
>> wonder if boot loader check uncompress size aka vmlinux size in bzImage
>> before it find one good position for bzImage...?
>>
>>     
>
> Jeremy's brk patches may break:
> 1. kexec load 64bit vmlinux on some ram that near the memory hole etc.
> blindly to use ram after _end may have some problem
> 2. coreboot aka linux is using elf (by mkelfImage : vmlinux + initrd), initrd became one section after _end...
> could cause initrd get overwrite... by extend _brk
>   

But its no different from what i386 does now to allocate its initial 
pagetables.  How does this not break now?

    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/