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>
Cc: rcu@vger.kernel.org, Kunwu Chan <kunwu.chan@gmail.com>,
Kunwu Chan <chentao@kylinos.cn>
Subject: [PATCH for-v7.5 07/11] rcu-tasks: Validate callback arguments
Date: Thu, 12 Nov 2026 19:50:09 -0500 [thread overview]
Message-ID: <20261113005017.2772440-8-jfern@kernel.org> (raw)
In-Reply-To: <20261113005017.2772440-1-jfern@kernel.org>
From: Kunwu Chan <kunwu.chan@gmail.com>
Check callback-head alignment and reject NULL callback
functions in the generic RCU Tasks callback registration path.
Reviewed-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
Reviewed-by: Joel Fernandes <jfern@kernel.org>
Signed-off-by: Joel Fernandes <jfern@kernel.org>
---
kernel/rcu/tasks.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/kernel/rcu/tasks.h b/kernel/rcu/tasks.h
index 0eec90464d64..a1883cf5b5d1 100644
--- a/kernel/rcu/tasks.h
+++ b/kernel/rcu/tasks.h
@@ -349,6 +349,13 @@ static void call_rcu_tasks_generic(struct rcu_head *rhp, rcu_callback_t func,
bool needwake;
struct rcu_tasks_percpu *rtpcp;
+ /* Misaligned rcu_head! */
+ WARN_ON_ONCE((unsigned long)rhp & (sizeof(void *) - 1));
+
+ /* Avoid NULL dereference if callback is NULL. */
+ if (WARN_ON_ONCE(!func))
+ return;
+
rhp->next = NULL;
rhp->func = func;
local_irq_save(flags);
--
2.54.0
next prev parent reply other threads:[~2026-11-13 0:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 0:50 [PATCH for-v7.5 00/11] RCU debug patches for v7.5 Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 01/11] rcu: Print CPU that preempted stalled reader wants to run on Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 02/11] srcu: Record callback registration stack for KASAN Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 03/11] srcutiny: " Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 04/11] rcu: Record callback registration stack for Tiny RCU Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 05/11] srcu: Validate callback arguments Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 06/11] rcu: Validate callback arguments in Tiny RCU Joel Fernandes
2026-11-13 0:50 ` Joel Fernandes [this message]
2026-11-13 0:50 ` [PATCH for-v7.5 08/11] srcu: Detect duplicate callback enqueue at registration Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 09/11] srcutiny: Detect duplicate callback enqueue Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 10/11] rcu-tasks: " Joel Fernandes
2026-11-13 0:50 ` [PATCH for-v7.5 11/11] rcu: Improve duplicate callback diagnostics 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=20261113005017.2772440-8-jfern@kernel.org \
--to=jfern@kernel.org \
--cc=boqun@kernel.org \
--cc=chentao@kylinos.cn \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kunwu.chan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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=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.