From: Kees Cook <keescook@chromium.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
Peter Jones <pjones@redhat.com>, Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] efi: remove deprecated 'efivars' sysfs interface
Date: Thu, 16 Jun 2022 09:20:52 -0700 [thread overview]
Message-ID: <202206160919.360DB5F4@keescook> (raw)
In-Reply-To: <20220616124740.580708-3-ardb@kernel.org>
On Thu, Jun 16, 2022 at 02:47:40PM +0200, Ard Biesheuvel wrote:
> Commit 5d9db883761a ("efi: Add support for a UEFI variable filesystem")
> dated Oct 5, 2012, introduced a new efivarfs pseudo-filesystem to
> replace the efivars sysfs interface that was used up to that point to
> expose EFI variables to user space.
>
> The main problem with the sysfs interface was that it only supported up
> to 1024 bytes of payload per file, whereas the underlying variables
> themselves are only bounded by a platform specific per-variable and
> global limit that is typically much higher than 1024 bytes.
>
> The deprecated sysfs interface is only enabled on x86 and Itanium, other
> EFI enabled architectures only support the efivarfs pseudo-filesystem.
Does anything still use the sysfs interface? (e.g. do paths to it exist
in anything meaningful in, say, a Debian code search?)
--
Kees Cook
next prev parent reply other threads:[~2022-06-16 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 12:47 [RFC PATCH 0/2] efi: get rid of deprecated sysfs varstore interface Ard Biesheuvel
2022-06-16 12:47 ` [RFC PATCH 1/2] selftests/kexec: remove broken EFI_VARS secure boot fallback check Ard Biesheuvel
2022-06-16 18:08 ` Mimi Zohar
2022-06-24 8:20 ` Ard Biesheuvel
2022-06-16 12:47 ` [RFC PATCH 2/2] efi: remove deprecated 'efivars' sysfs interface Ard Biesheuvel
2022-06-16 16:20 ` Kees Cook [this message]
2022-06-16 16:32 ` Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202206160919.360DB5F4@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox