mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Prashant Singh <singhpra@juniper.net>
To: Ard Biesheuvel <ardb@kernel.org>,
	"Luis Claudio R . Goncalves" <lgoncalv@redhat.com>,
	Steve McIntyre <93sam@debian.org>, Jeremy Kerr <jk@ozlabs.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	"Clark Williams" <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>, <linux-doc@vger.kernel.org>,
	<linux-rt-devel@lists.linux.dev>
Subject: Re: [PATCH v2] efivarfs: add nostatfs mount option to skip QueryVariableInfo()
Date: Thu, 24 Sep 2026 18:45:28 -0700	[thread overview]
Message-ID: <20260925014528.2015-1-singhpra@juniper.net> (raw)
In-Reply-To: <0d23d4f2-b5b8-47c3-a676-f6ec72ecf45d@app.fastmail.com>

On Thu, 24 Sep 2026, at 13:59, Ard Biesheuvel wrote:
> On Thu, 24 Sep 2026, at 13:36, Luis Claudio R. Goncalves wrote:
>> In this case, corroborating with Sashiko findings, it is necessary to
>> have a way to override that default in kernels with PREEMPT_RT enabled.
>> To be used where this is required for firmware updates.
>
> Indeed.

Agreed -- and thanks Luis and Steve for catching the fwupd impact.

For v3 I'll make the option a negatable flag: "nostatfs" skips
QueryVariableInfo() (and remains the default on PREEMPT_RT), while
"statfs" forces reporting back on. So on an RT kernel, mounting efivarfs
with -o statfs restores the free-space reporting that fwupd needs for
KEK/DB/DBX updates, while the default still avoids the preempt-disabled
firmware call.

I'll send v3 with that change shortly.

Thanks,
Prashant

  reply	other threads:[~2026-09-25  1:46 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
2026-09-24 11:36     ` Luis Claudio R. Goncalves
2026-09-24 11:59       ` Ard Biesheuvel
2026-09-25  1:45         ` Prashant Singh [this message]
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=20260925014528.2015-1-singhpra@juniper.net \
    --to=singhpra@juniper.net \
    --cc=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 \
    /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®