linux-kernel - Re: [PATCH v6 18/27] x86, boot: add fields to support load bzImage and ramdisk 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: <CAE9FiQXypjnEM60OvZXx8n9LaLexoyeE1zau1bE1YuHN1fmG_w@mail.gmail.com>
Date:	Thu, 13 Dec 2012 15:28:44 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Rob Landley <rob@...dley.net>,
	Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH v6 18/27] x86, boot: add fields to support load bzImage
 and ramdisk above 4G

On Thu, Dec 13, 2012 at 2:54 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> 0x1f0 is unsuitable for use as sentinel -- or in fact for any purpose --
> because it is quite plausible that someone may (fairly sanely) start the
> copy range at 0x1f0 instead of 0x1f1... we really should have documented
> it that way but it is too late now.
>
> However, we can use 0x1ef.

right. updated to use 0x1ef.

Thanks

Yinghai

Download attachment "ext_ramdisk_image_v6_1.patch" of type "application/octet-stream" (10212 bytes)