| 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
| ||
|
Date: Wed, 05 Mar 2014 08:40:45 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Borislav Petkov <bp@...en8.de>, Vivek Goyal <vgoyal@...hat.com> CC: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, ebiederm@...ssion.com, mjg59@...f.ucam.org, greg@...ah.com, jkosina@...e.cz Subject: Re: [PATCH 08/11] kexec-bzImage: Support for loading bzImage using 64bit entry On 03/05/2014 08:37 AM, Borislav Petkov wrote: >> >> If the "HdrS" (0x53726448) magic number is not found at offset 0x202, >> the boot protocol version is "old". Loading an old kernel, the >> following parameters should be assumed: >> >> Image type = zImage >> initrd not supported >> Real-mode kernel must be located at 0x90000. >> >> So if it is old version then it is zImage (and not bzImage). So pr_debug() >> message seems to be correct that image one is trying to load is not >> bzImage and this loader will not handle this image. > > Ok, old == zImage, got it. > No, old ⊂ zImage, but you can have a zImage with a newer protocol version, too. There are no load flags in the old protocol. These days the old protocol is interesting mostly because of non-Linux images using the same boot protocol. -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/
Powered by blists - more mailing lists