From: Richard Lyu <richard.lyu@suse.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, x86@kernel.org,
stable@vger.kernel.org, Anisse Astier <anisse@astier.eu>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH] efivarfs: Rate limit statfs() handler
Date: Thu, 20 Aug 2026 21:16:55 +0800 [thread overview]
Message-ID: <aob-R-ULD6S38waw@r1chard> (raw)
In-Reply-To: <20260818141150.905336-1-ardb@kernel.org>
On 2026/08/18 16:11, Ard Biesheuvel wrote:
>Ravi reports that statfs() may be called by unprivileged users on the
>efivarfs mount point, which may result in a flood of calls to the
>QueryVariableInfo() runtime service. These calls are disproportionately
>costly on x86 systems where the variable store is backed by SMM, as each
>SMM entry requires a rendez-vous of all the CPUs.
>
>So rate limit the calls to QueryVariableInfo() at twice per second, and
>return the most recently obtained values for calls that are elided.
>
>Cc: <stable@vger.kernel.org>
>Cc: Anisse Astier <anisse@astier.eu>
>Reported-by: Ravi Bangoria <ravi.bangoria@amd.com>
>Fixes: d86ff3333cb1 ("efivarfs: expose used and total size")
>Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
>---
>This supersedes [0], which had some issues, the main one being that a
>cache that requires explicit invalidation may go out of sync due to
>direct calls to SetVariable() made by other drivers.
>
>[0] https://lore.kernel.org/all/20260801144258.15977-2-ardb@kernel.org/
>
> fs/efivarfs/super.c | 30 ++++++++++++++++----
> 1 file changed, 24 insertions(+), 6 deletions(-)
>
>diff --git a/fs/efivarfs/super.c b/fs/efivarfs/super.c
>index 733c19571f1c..8d33f11db2a1 100644
>--- a/fs/efivarfs/super.c
>+++ b/fs/efivarfs/super.c
>@@ -89,12 +89,30 @@ static int efivarfs_statfs(struct dentry *dentry, struct kstatfs *buf)
> /* Some UEFI firmware does not implement QueryVariableInfo() */
> storage_space = remaining_space = 0;
> if (efi_rt_services_supported(EFI_RT_SUPPORTED_QUERY_VARIABLE_INFO)) {
>- status = efivar_query_variable_info(attr, &storage_space,
>- &remaining_space,
>- &max_variable_size);
>- if (status != EFI_SUCCESS && status != EFI_UNSUPPORTED)
>- pr_warn_ratelimited("query_variable_info() failed: 0x%lx\n",
>- status);
>+ static DEFINE_RATELIMIT_STATE(_rs, 2 * HZ, 5);
>+ static u64 storage, remaining;
>+ static DEFINE_SPINLOCK(lock);
>+
>+ if (!__ratelimit(&_rs)) {
>+ ratelimit_set_flags(&_rs, RATELIMIT_MSG_ON_RELEASE);
>+
>+ spin_lock(&lock);
>+ storage_space = storage;
>+ remaining_space = remaining;
>+ spin_unlock(&lock);
>+ } else {
>+ status = efivar_query_variable_info(attr, &storage_space,
>+ &remaining_space,
>+ &max_variable_size);
>+ if (status != EFI_SUCCESS && status != EFI_UNSUPPORTED)
>+ pr_warn("query_variable_info() failed: 0x%lx\n",
>+ status);
>+
>+ spin_lock(&lock);
>+ storage = storage_space;
>+ remaining = remaining_space;
>+ spin_unlock(&lock);
>+ }
> }
>
> /*
>--
>2.55.0.699.gb54405d56f-goog
>
>
Reviewed-by: Richard Lyu <richard.lyu@suse.com>
prev parent reply other threads:[~2026-08-20 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 14:11 [PATCH] efivarfs: Rate limit statfs() handler Ard Biesheuvel
2026-08-19 16:29 ` Anisse Astier
2026-08-19 16:36 ` Ard Biesheuvel
2026-08-20 13:16 ` Richard Lyu [this message]
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=aob-R-ULD6S38waw@r1chard \
--to=richard.lyu@suse.com \
--cc=anisse@astier.eu \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.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