From: Joel Fernandes <jfern@kernel.org>
To: linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>,
Joel Fernandes <jfern@kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun@kernel.org>,
Uladzislau Rezki <urezki@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang@linux.dev>, Guo Ren <guoren@kernel.org>
Cc: rcu@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
stable@vger.kernel.org, Joel Fernandes <joelagnelf@nvidia.com>,
linux-csky@vger.kernel.org
Subject: [PATCH for-v7.5 1/5] srcu: Select IRQ_WORK for Tiny SRCU
Date: Thu, 12 Nov 2026 19:49:40 -0500 [thread overview]
Message-ID: <20261113004946.2758197-2-jfern@kernel.org> (raw)
In-Reply-To: <20261113004946.2758197-1-jfern@kernel.org>
Tiny SRCU uses irq_work_queue() to start grace periods and
irq_work_sync() to wait for pending work. However, TINY_SRCU does not
select IRQ_WORK, so configurations that do not otherwise enable it
fail to link with undefined references to these functions.
Guenter reported this failure with csky tinyconfig on the 6.12 and
6.6 stable trees. Current kernels enable IRQ_WORK indirectly through
SLUB, but Tiny SRCU should declare its own dependency.
Select IRQ_WORK from TINY_SRCU to ensure that its irq_work calls are
supported independently of other configuration options.
Fixes: a6fc88b22bc8 ("srcu: Use irq_work to start GP in tiny SRCU")
Reported-by: Guenter Roeck <linux@roeck-us.net>
Closes: https://lore.kernel.org/r/49da816c-8082-46f1-bb12-f0d6187bb06a@roeck-us.net/
Suggested-by: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org
Signed-off-by: Joel Fernandes <jfern@kernel.org>
---
kernel/rcu/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/rcu/Kconfig b/kernel/rcu/Kconfig
index bc9483c0b5d8..b6d3597758fc 100644
--- a/kernel/rcu/Kconfig
+++ b/kernel/rcu/Kconfig
@@ -56,6 +56,7 @@ config RCU_EXPERT
config TINY_SRCU
bool
default y if TINY_RCU
+ select IRQ_WORK
help
This option selects the single-CPU non-preemptible version of SRCU.
--
2.54.0
next prev parent reply other threads:[~2026-11-13 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 0:49 [PATCH for-v7.5 0/5] RCU core patches for v7.5 Joel Fernandes
2026-11-13 0:49 ` Joel Fernandes [this message]
2026-11-13 0:49 ` [PATCH for-v7.5 2/5] rcu-tasks: Avoid alloc_percpu() failure in rcu_tasks_rude_wait_gp() Joel Fernandes
2026-11-13 0:49 ` [PATCH for-v7.5 3/5] rcu: assert static storage for RCU sync and SRCU definitions Joel Fernandes
2026-11-13 0:49 ` [PATCH for-v7.5 4/5] rcu-tasks: Use pr_debug() for callback contend/collapse messages Joel Fernandes
2026-11-13 1:01 ` Joel Fernandes
2026-11-13 0:49 ` [PATCH for-v7.5 5/5] cpuhp: Expedite RCU when toggling system-wide SMT mode Joel Fernandes
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=20261113004946.2758197-2-jfern@kernel.org \
--to=jfern@kernel.org \
--cc=boqun@kernel.org \
--cc=frederic@kernel.org \
--cc=guoren@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mathieu.desnoyers@efficios.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.org \
--cc=urezki@gmail.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 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.