linux-kernel - Re: [PATCH v7u1 00/31] x86, boot, 64bit: Add support for loading ramdisk and bzImage above 4G

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:	Mon, 14 Jan 2013 15:50:18 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Borislav Petkov <bp@...en8.de>, Jan Kiszka <jan.kiszka@....de>,
	Jason Wessel <jason.wessel@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7u1 00/31] x86, boot, 64bit: Add support for loading
 ramdisk and bzImage above 4G

On 01/14/2013 03:39 PM, David Woodhouse wrote:
> On Mon, 2013-01-14 at 15:16 -0800, H. Peter Anvin wrote:
>> The reason I want to do this this way is that I want to also make
>> David Woodhouse's protocol fixes to make the EFI stub work correctly
>> at the same time, so we get a single protocol level bump. 
> 
> My changes don't need a protocol level bump. It's just two new bits in
> load_flags that old loaders won't care about.
> 

I'm wondering if we should put your new flags in xloadflags instead just
because some boot loaders have been known to clobber the loadflags when
setting the upper bits.  In theory it shouldn't matter... I'm wondering
if it does in practice.  The other bit is that Yinghai's changes want
even more flags.

Either way might as well see if we can do it as closely adjacently as
possible (but no, I don't want to drag this out.)

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