linux-kernel - Re: does boot loader check uncompressed kernel size?

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, 28 Feb 2009 00:08:05 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Cyrill Gorcunov <gorcunov@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: does boot loader check uncompressed kernel size?

Yinghai Lu wrote:
> On Fri, Feb 27, 2009 at 11:47 PM, Cyrill Gorcunov <gorcunov@...il.com> wrote:
>> [Yinghai Lu - Fri, Feb 27, 2009 at 11:39:06PM -0800]
>> | wonder if boot loader check uncompress size aka vmlinux size in bzImage
>> | before it find one good position for bzImage...?
>> |
>> | YH
>> |
>>
>> At least for x86-64 in grub-1.96 I didn't find such a check.
>> Btw, but why should it care? Or you mean something else?
> 
> thinking about Jeremy's brk patches that may use ram after _end blindly...
> 

We already do that.  Jeremy's brk patches just formalizes it.

	-hpa

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