| 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
| ||
|
Message-ID: <20070429045024.GA27000@in.ibm.com> Date: Sun, 29 Apr 2007 10:20:24 +0530 From: Vivek Goyal <vgoyal@...ibm.com> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: "H. Peter Anvin" <hpa@...or.com>, Jeff Garzik <jeff@...zik.org>, Andi Kleen <ak@...e.de>, patches@...-64.org, linux-kernel@...r.kernel.org Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage On Sat, Apr 28, 2007 at 02:46:18PM -0600, Eric W. Biederman wrote: > "H. Peter Anvin" <hpa@...or.com> writes: > > > Eric W. Biederman wrote: > >> > >> The boot protocol change is in 2.6.21 for arch/i386. > >> > >> HPA looked at it a while ago. > >> > >> All it does is set a flag that tells a bootloader. > >> "Hey. I can run when loaded a non-default address, and this is what > >> you have to align me to." > >> > >> All relocation processing happens in the kernel itself. > >> > >> So it is all pretty trivial. > >> > > > > Indeed. We *did* find some problems with Grub with the early versions, > > those were addressed. > > We found some failures that weren't root caused so we went to this > more conservative version. > > RHEL5 is actually shipping the original version of these patches if I > recall correctly. > Yes, RHEL5 is shipping original version of patches where an where and ELF header has been added to describe bzImage. Thanks Vivek - 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/
Powered by blists - more mailing lists