linux-kernel - Re: [RFC] fs: make efivarfs a pseudo filesystem, built by default with 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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150105141521.GC3163@console-pimps.org>
Date:	Mon, 5 Jan 2015 14:15:21 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Leif Lindholm <leif.lindholm@...aro.org>
Cc:	linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, viro@...iv.linux.org.uk,
	matthew.garrett@...ula.com, jk@...abs.org, matt.fleming@...el.com,
	pjones@...hat.com
Subject: Re: [RFC] fs: make efivarfs a pseudo filesystem, built by default
 with EFI

On Thu, 18 Dec, at 05:50:49PM, Leif Lindholm wrote:
> efivars is currently enabled under MISC_FILESYSTEMS, which is decribed
> as "such as filesystems that came from other operating systems".
> In reality, it is a pseudo filesystem, providing access to the kernel
> UEFI variable interface.
> 
> Since this is the preferred interface for accessing UEFI variables, over
> the legacy efivars interface, also build it by default as a module if
> CONFIG_EFI.
> 
> Signed-off-by: Leif Lindholm <leif.lindholm@...aro.org>
> ---
>  fs/Kconfig          | 2 +-
>  fs/efivarfs/Kconfig | 1 +
>  2 files changed, 2 insertions(+), 1 deletion(-)

Looks good to me Leif.

Unless I hear otherwise, I'll apply this to the 'next' branch of the EFI
tree this week.

-- 
Matt Fleming, Intel Open Source Technology Center
--
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/