From: Steve McIntyre <93sam@debian.org>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Prashant Singh <singhpra@juniper.net>,
Ard Biesheuvel <ardb@kernel.org>, Jeremy Kerr <jk@ozlabs.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v2] efivarfs: add nostatfs mount option to skip QueryVariableInfo()
Date: Thu, 24 Sep 2026 12:19:23 +0100 [thread overview]
Message-ID: <20260924111913.GN3447081@tack.einval.com> (raw)
In-Reply-To: <arUD_p0Vn4qyBH_e@redhat.com>
Hey all,
On Thu, Sep 24, 2026 at 08:05:34AM -0300, Luis Claudio R. Goncalves wrote:
>On Fri, Sep 18, 2026 at 09:41:24PM -0700, Prashant Singh wrote:
>
>I tested the patch and was quite satisfied with the results, but upon a
>comment from colleagues I ran a few more tests and noticed (confirmed their
>hunch) that fwupd complains about not being able to get the free space in
>efivars:
>
> # fwupdmgr get-devices | grep efivars
> │ Update Error: getting efivars free space is not supported
> │ │ Update Error: getting efivars free space is not supported
> ...
>
>I was not able to establish whether that would prevent specific operations
>due to the HW I had available for such test.
fwupd will refuse to do some of its updates if it can't read the
efivars free space, in particular updates of the secure boot keyrings
like KEK/DB/DBX.
--
Steve McIntyre, Cambridge, UK. 93sam@debian.org
next prev parent reply other threads:[~2026-09-24 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 4:41 Prashant Singh
2026-09-19 4:50 ` sashiko-bot
2026-09-19 14:51 ` Ard Biesheuvel
2026-09-24 10:56 ` Ard Biesheuvel
2026-09-24 11:05 ` Luis Claudio R. Goncalves
2026-09-24 11:12 ` Ard Biesheuvel
2026-09-24 11:19 ` Steve McIntyre [this message]
2026-09-24 11:36 ` Luis Claudio R. Goncalves
2026-09-24 11:59 ` Ard Biesheuvel
2026-09-25 1:45 ` Prashant Singh
2026-09-25 6:14 ` Sebastian Andrzej Siewior
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=20260924111913.GN3447081@tack.einval.com \
--to=93sam@debian.org \
--cc=ardb@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=corbet@lwn.net \
--cc=jk@ozlabs.org \
--cc=lgoncalv@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=singhpra@juniper.net \
/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
all inboxes | Powered by JetHome®