linux-kernel - Re: [PATCH -v2 0/4] EFI 1:1 mapping

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: <20130620092237.GA6943@gmail.com>
Date:	Thu, 20 Jun 2013 11:22:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Borislav Petkov <bp@...en8.de>,
	Linux EFI <linux-efi@...r.kernel.org>,
	Matt Fleming <matt@...sole-pimps.org>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>, Borislav Petkov <bp@...e.de>
Subject: Re: [PATCH -v2 0/4] EFI 1:1 mapping


* Matthew Garrett <mjg59@...f.ucam.org> wrote:

> On Thu, Jun 20, 2013 at 11:13:21AM +0200, Ingo Molnar wrote:
> 
> > Cool - and supposedly this will work in a Mac environment as well? Would 
> > be very nice to avoid fundamentally fragile system specific quirks for 
> > something as fundamental as the EFI runtime memory mapping model ...
> 
> Apple is the only case where I'd expect there to be an issue, since they 
> only started supporting booting Windows via UEFI on very recent systems. 
> However, unless they're actually sniffing the page tables on UEFI entry, 
> I can't see any way that this could break things???

Agreed - I was susprised to see that the runtime was able to _break_ in 
any way due to 1:1: my assumption was that it can only get better.

But I did not realize that the 1:1 boot flag also changed what was passed 
down, which probably explains the breakages.

I'd even argue to not do this whole boot flag thing at all - just 
standardize on the Windows compatibility model as closely as possible.

Thanks,

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