linux-kernel - Re: [BUG] Linux 3.14 fails to boot with new EFI changes

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

Message-ID: <20140130221950.GJ3105@sgi.com>
Date:	Thu, 30 Jan 2014 16:19:50 -0600
From:	Alex Thorlton <athorlton@....com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Matt Fleming <matt@...sole-pimps.org>,
	Russ Anderson <rja@....com>, linux-kernel@...r.kernel.org
Subject: Re: [BUG] Linux 3.14 fails to boot with new EFI changes

Re-adding lkml.

Here's what we've got as far as your questions go (snipped from an
e-mail from Russ):

<snip>
> * what kind of a pointer is that, physical address, or?

The quick answer is I think it is a virtual address, because                                                                                                                                                                                                                                                                 
it does not work in physical mode.  If you ever see "virtefi"                                                                                                                                                                                                                                                                
on the RHEL bootline it is because RH switched the default                                                                                                                                                                                                                                                                   
to physical mode, which caused UV to not boot.  "virtefi"                                                                                                                                                                                                                                                                    
forced it back to virtual mode.

> * does it get switched to a virtual address after
> SetVirtualAddressMap()?

I believe SetVirtualAddressMap() creates the virtual mappings,                                                                                                                                                                                                                                                               
but I would have to look at the code to be sure.

> * Which region in your UEFI map contains that function, what are the
> modalities about mapping it?

Not sure about the region.  The MMRs are in a uncached range                                                                                                                                                                                                                                                                 
and the functions are cached marked executable.  But have to                                                                                                                                                                                                                                                                 
double check on that.
</snip>

> * Anything else I should know?

Probably, but nothing that's jumping out at us right now :)

Let us know if you need anything else.

Thanks!

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