linux-kernel - Re: [RFC] [PATCH] Allow empty e820 map if EFI map will be provided later.

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] [day] [month] [year] [list]

Message-ID: <AANLkTinTS9q_mYcC2Q6HKHJt_XeLc11j-vc7Iu9HKZpQ@mail.gmail.com>
Date:	Wed, 2 Jun 2010 09:24:04 -0700
From:	Bill Richardson <wfrichar@...omium.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	akpm@...ux-foundation.org, fweisbec@...il.com, yinghai@...nel.org,
	pavel@....cz, shane.wang@...el.com, linux-kernel@...r.kernel.org,
	olofj@...omium.org, msb@...omium.org, drewry@...omium.org
Subject: Re: [RFC] [PATCH] Allow empty e820 map if EFI map will be provided 
	later.

On Wed, Jun 2, 2010 at 9:14 AM, H. Peter Anvin <hpa@...or.com> wrote:
>
> No!  Bloody **** hell no!

Heh. Well, that answers that.


> This was settled in 2007 -- it is the boot loaders duty to provide a memory map.  The fact that we allowed a
> hack in to let the kernel itself add additional ranges from EFI has proven to be an utter mistake, and this is
> yet another example of it.

Ah. With that hint, I've now found some of the original discussion.
Sorry I missed it before. Having dealt with EFI for some weeks now, I
can't say I find your reaction overstated.

Thanks for the quick response.

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