linux-kernel - Re: [PATCH] efi: add efi

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: <4FEB80A5.8020806@zytor.com>
Date:	Wed, 27 Jun 2012 14:52:37 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Olof Johansson <olof@...om.net>
CC:	Marko Kohtala <marko.kohtala@...il.com>,
	linux-kernel@...r.kernel.org, mjg@...hat.com
Subject: Re: [PATCH] efi: add efi_runtime state checking

On 06/27/2012 02:35 PM, Olof Johansson wrote:
> This adds an efi_runtime variable indicating whether the
> efi runtime services are available. The only time they are
> expected to not be available is when a 32-bit kernel has been
> booted using 64-but EFI and vice versa.
>
> It also adds checking to the two locations where functions are
> called; x86 reboot and efivars.
>

OK, stupid question:

Why is this different from the efi_enabled variable, or rather: why is 
it different from what the efi_enabled variable *should* be?  If runtime 
services aren't available the only "EFI" that is available to the kernel 
are the data structures passed in, and those can be checked directly...

	-hpa


-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.



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