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: Fri, 22 Nov 2013 14:30:17 +0100 (CET) From: Jiri Kosina <jkosina@...e.cz> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Vivek Goyal <vgoyal@...hat.com>, "Eric W. Biederman" <ebiederm@...ssion.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, kexec@...ts.infradead.org, "H. Peter Anvin" <hpa@...or.com>, Matthew Garrett <mjg59@...f.ucam.org>, Greg Kroah-Hartman <greg@...ah.com> Subject: Re: [PATCH 0/6] kexec: A new system call to allow in kernel loading On Fri, 22 Nov 2013, Geert Uytterhoeven wrote: > > Why ELF case is so interesting. I have not use kexec to boot ELF > > images in years and have not seen others using it too. In fact bzImage > > seems to be the most common kernel image format for x86, most of the distros > > ship and use. > > > > So first I did the loader for the common use case. There is no reason > > that one can't write another loader for ELF images. It just bloats > > the code. Hence I thought that other image loaders can follow slowly. I am > > not sure why do you say that bzImage is uninteresting. > > Welcome to the non-x86-centric world ;-) > > Looking at kexec-tools, all of arm, cris, i386, ia64, m68k, mips, ppc, ppc64, > s390, sh, and x86_64 support ELF. > Only arm, i386, ppc, ppc64, sh, and x86_64 support zImage. > It's not clear to me what alpha supports (if it supports anything at all?). OTOH, does this feature make any sense whatsover on architectures that don't support secure boot anyway? -- Jiri Kosina SUSE Labs -- 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