All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Prashant Singh <singhpra@juniper.net>,
	Jeremy Kerr <jk@ozlabs.org>,
	Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Steve McIntyre <93sam@debian.org>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v4] efivarfs: add nostatfs mount option to skip QueryVariableInfo()
Date: Tue, 29 Sep 2026 17:14:01 +0200	[thread overview]
Message-ID: <20260929151401.doOQX7D0@linutronix.de> (raw)
In-Reply-To: <59d5452c-42b1-4784-a593-5e549a2a0f12@app.fastmail.com>

On 2026-09-29 14:22:31 [+0200], Ard Biesheuvel wrote:
> Hi Sebastian,
Hi Ard,

> Thanks for taking a look.

doing my best…

> >> --- a/fs/efivarfs/internal.h
> >> +++ b/fs/efivarfs/internal.h
> >> @@ -11,6 +11,7 @@
> >>  struct efivarfs_mount_opts {
> >>  	kuid_t uid;
> >>  	kgid_t gid;
> >> +	bool nostatfs;		/* skip QueryVariableInfo() in statfs() */
> > Here and below you add a comment to every change you make. What about
> > focusing on the important parts, that deserve an explanation why a
> > change has been made. For instance why nostatfs has the READ_ONCE/
> > WRITE_ONCE accessors and sometimes it does not.
> >
> 
> AIUI the READ_ONCE/WRITE_ONCE were added because Sashiko warned about
> potential KCSAN splats? It would be nice to mention that.

:)

> In any case, KCSAN is runtime instrumentation, and efi_reboot_required()
> is only called after all other CPUs have been brought down. So if anything,
> this should just wrap the read on the reboot path in a data_race() so
> that we don't trigger any instrumentation inadvertently on the way down.

Right. So if anything, there could be a data_race() in one place instead
inconsistent READ/ WRITE once as we have it now.

Sebastian

  reply	other threads:[~2026-09-29 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 20:34 [PATCH v4] efivarfs: add nostatfs mount option to skip QueryVariableInfo() Prashant Singh
2026-09-28 20:47 ` sashiko-bot
2026-09-29  6:32 ` Ard Biesheuvel
2026-09-29  7:43 ` Sebastian Andrzej Siewior
2026-09-29 12:22   ` Ard Biesheuvel
2026-09-29 15:14     ` Sebastian Andrzej Siewior [this message]
2026-09-30  1:35       ` Prashant Singh
2026-09-30  6:09         ` Ard Biesheuvel
2026-09-30  6:32         ` Sebastian Andrzej Siewior
2026-10-01  1:20           ` Prashant Singh
2026-10-04  7:58             ` Ard Biesheuvel
2026-10-04 14:43               ` MaeeFilho FL
2026-10-05 23:35                 ` Prashant Singh

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=20260929151401.doOQX7D0@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=93sam@debian.org \
    --cc=ardb@kernel.org \
    --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=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=singhpra@juniper.net \
    --cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.