From: "Luck, Tony" <tony.luck@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Dumazet <edumazet@google.com>,
Reinette Chatre <reinette.chatre@intel.com>,
<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>
Subject: [PATCH v2] once: Don't use a work queue to reset sleepable static key
Date: Mon, 12 Jan 2026 10:08:53 -0800 [thread overview]
Message-ID: <aWU4tfTju1l3oZCu@agluck-desk3> (raw)
In-Reply-To: <20260108232717.14411-1-tony.luck@intel.com>
Pointless overhead to use a work queue to reset the static key
for a DO_ONCE_SLEEPABLE() invocation.
Note that the previous code path included a BUG_ON() if the static key
was already disabled. Dropped that as part of this change because:
1) Use of BUG_ON() is highly discouraged.
2) There is a WARN_ON() in the static_branch_disable() code path
that would provide adequate breadcrumbs to debug any issue.
Reported-by: Reinette Chatre <reinette.chatre@intel.com>
Signed-off-by: Tony Luck <tony.luck@intel.com>
---
Changes since v1:
Andrew Morton pointed out that adding a new BUG_ON() was ill-advised.
Drop it (but explain why it isn't needed in the commit message).
lib/once.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/once.c b/lib/once.c
index 2c306f0e891e..8557eb489f34 100644
--- a/lib/once.c
+++ b/lib/once.c
@@ -93,6 +93,6 @@ void __do_once_sleepable_done(bool *done, struct static_key_true *once_key,
{
*done = true;
mutex_unlock(&once_mutex);
- once_disable_jump(once_key, mod);
+ static_branch_disable(once_key);
}
EXPORT_SYMBOL(__do_once_sleepable_done);
--
2.52.0
prev parent reply other threads:[~2026-01-12 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 23:27 [PATCH] once: Don't use a work queue to reset sleepable static key Tony Luck
2026-01-09 0:33 ` Reinette Chatre
2026-01-11 2:54 ` Andrew Morton
2026-01-12 18:08 ` Luck, Tony [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=aWU4tfTju1l3oZCu@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=reinette.chatre@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