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]

Message-ID: <50F491E2.8090907@zytor.com>
Date:	Mon, 14 Jan 2013 15:16:50 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	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, David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH v7u1 00/31] x86, boot, 64bit: Add support for loading
 ramdisk and bzImage above 4G

On 01/14/2013 02:44 PM, Yinghai Lu wrote:
> On Mon, Jan 14, 2013 at 12:45 PM, H. Peter Anvin <hpa@...or.com> wrote:
>> This is getting extremely unwieldy and we need to get it broken up a bit.
>>
>> I would really like to get the boot protocol changes earlier in the
>> series, because it has interactions with work other people are doing and
>> may need additional surgery.  That is, the additions of flags and fields
>> to make it possible for the kernel to indicate that > 4 GB booting is
>> possible, not the actual implementation thereof.  This split between
>> protocol changes and implementation will also be useful for bisection.
> 
> When will we actually change protocol version number in the code?
> 
> We need to refer that number in the protocol doc.
> 

The protocol change and the documentation go together (as separate but
adjacent patches).  We bump the number when we change the structure to
accommodate the necessary fields and flags (i.e. a vacuous
implementation), not when we add the full functionality.

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.  I think it is better
I merge both sets, and I was hoping to do that tomorrow if possible.

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