linux-kernel - Re: bzImage 2.12

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: <1359313804.10797.74.camel@shinybook.infradead.org>
Date:	Sun, 27 Jan 2013 19:10:04 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Matt Fleming <matt.fleming@...el.com>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Gokul Caushik <caushik1@...il.com>,
	Josh Triplett <josh@...htriplett.org>,
	Joe Millenbach <jmillenbach@...il.com>
Subject: Re: bzImage 2.12

On Sun, 2013-01-27 at 11:02 -0800, H. Peter Anvin wrote:
> This is intentionally a protocol only patch, which may be possible to 
> push into 3.8 as an urgent patch.  David, if I understand our 
> discussions right it might be better to not export XLF_EFI_HANDOFF_32
> at this time?

That won't stop broken bootloaders from jumping to $handover_offset
anyway. Anyone who was daft enough to implement EFI boot stub in their
bootloader *despite* its obvious brokenness, rather than insisting on
fixing it before it could be considered usable, will still be jumping
into hyperspace. I have little sympathy for them, but I'm told we need
to care.

It'd probably be better to just mark CONFIG_EFI_STUB as 'depends on
BROKEN' for 32-bit.

Or, and perhaps this is heresy, merge the patches which bloody fix it?

-- 
dwmw2

Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (6171 bytes)