linux-kernel - Re: [PATCH 4/8] x86 boot: allow overlapping ebda and efi memmap memory ranges

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: <4856A6F9.3090605@zytor.com>
Date:	Mon, 16 Jun 2008 10:46:33 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Paul Jackson <pj@....com>
CC:	ying.huang@...el.com, mingo@...e.hu, tglx@...utronix.de,
	yhlu.kernel@...il.com, steiner@....com, travis@....com,
	linux-kernel@...r.kernel.org, andi@...stfloor.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 4/8] x86 boot: allow overlapping ebda and efi memmap memory
 ranges

Paul Jackson wrote:
> 
> The question to me is this.  Are there PCs which (1) need such a safety
> reservation of an ebda area -and- (2) boot with EFI enabled?  I am not
> asking if there -could- be (in the abstract, there certainly is no law
> of government or physics prohibiting such).  Rather I am asking as a
> practical matter if there is, or is likely to be, such PCs "in the wild."
> 
> The safety reservation of this ebda area is a hack.  As hacks go, it is
> a rather gentle hack, but still it is a hack.  As such, it is to be
> avoided unless there is a practical need.  Some non-efi old PCs have that
> need - no debate there.
> 
> Should we perpeturate this (gentle) hack for EFI systems as well?
> 

We *are* going to have similar hacks.  That's not a question.  At this 
point, the live pool of EFI systems is functionally zero, so it's 
pointless to try to draw conclusions from the live pool (the little I 
have heard about the incoming set of EFI machines make me think the 
problems we've had with BIOS will look like child's play compared to the 
EFI braindamages we'll have to suffer.)

Perpetuating this hack will cost a few kilobytes of memory on machines 
which may not care.  *Not* perpetuating may save a few kilobytes on 
machines which may cause odd behaviours that only are noticeable when 
you, say, boot from one OS into another.

Guess which option I think is saner.

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