From: Kunwu Chan <kunwu.chan@gmail.com>
To: jiangshanlai@gmail.com, paulmck@kernel.org,
josh@joshtriplett.org, work@onurozkan.dev, frederic@kernel.org,
neeraj.upadhyay@kernel.org, joelagnelf@nvidia.com,
boqun@kernel.org, urezki@gmail.com
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
qiang.zhang@linux.dev, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org, Kunwu Chan <kunwu.chan@gmail.com>,
Kunwu Chan <chentao@kylinos.cn>
Subject: [PATCH v2 10/10] rcu: Improve duplicate callback diagnostics
Date: Tue, 27 Oct 2026 15:09:23 +0800 [thread overview]
Message-ID: <20261027070923.3054462-11-kunwu.chan@gmail.com> (raw)
In-Reply-To: <20261027070923.3054462-1-kunwu.chan@gmail.com>
Use ratelimited diagnostics with dump_stack() for duplicate
callback detection in rcu_do_enqueue().
Suggested-by: Paul E. McKenney <paulmck@kernel.org>
Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
---
kernel/rcu/tree.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
index aea3aef7397e..a8ede50dbeff 100644
--- a/kernel/rcu/tree.c
+++ b/kernel/rcu/tree.c
@@ -25,6 +25,7 @@
#include <linux/rcupdate_wait.h>
#include <linux/interrupt.h>
#include <linux/llist.h>
+#include <linux/ratelimit.h>
#include <linux/sched.h>
#include <linux/sched/debug.h>
#include <linux/nmi.h>
@@ -3154,9 +3155,12 @@ static void check_cb_ovld(struct rcu_data *rdp)
* already disabled, and a drain of a remote CPU re-issues onto the draining
* CPU.
*/
+static DEFINE_RATELIMIT_STATE(rcu_dup_rs,
+ DEFAULT_RATELIMIT_INTERVAL,
+ DEFAULT_RATELIMIT_BURST);
+
static void rcu_do_enqueue(struct rcu_head *head, rcu_callback_t func, bool lazy_in)
{
- static atomic_t doublefrees;
unsigned long flags;
bool lazy;
struct rcu_data *rdp;
@@ -3167,9 +3171,10 @@ static void rcu_do_enqueue(struct rcu_head *head, rcu_callback_t func, bool lazy
* Use rcu:rcu_callback trace event to find the previous
* time callback was passed to call_rcu().
*/
- if (atomic_inc_return(&doublefrees) < 4) {
+ if (__ratelimit(&rcu_dup_rs)) {
pr_err("%s(): Double-freed CB %p->%pS()!!! ", __func__, head, head->func);
mem_dump_obj(head);
+ dump_stack();
}
WRITE_ONCE(head->func, rcu_leak_callback);
return;
--
2.43.0
prev parent reply other threads:[~2026-10-27 7:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 7:09 [PATCH v2 00/10] rcu: Improve callback diagnostics and validation Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 01/10] srcu: Record callback registration stack for KASAN Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 02/10] srcutiny: " Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 03/10] rcu: Record callback registration stack for Tiny RCU Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 04/10] srcu: Validate callback arguments Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 05/10] rcu: Validate callback arguments in Tiny RCU Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 06/10] rcu-tasks: Validate callback arguments Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 07/10] srcu: Detect duplicate callback enqueue at registration Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 08/10] srcutiny: Detect duplicate callback enqueue Kunwu Chan
2026-10-27 7:09 ` [PATCH v2 09/10] rcu-tasks: " Kunwu Chan
2026-10-27 7:09 ` Kunwu Chan [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=20261027070923.3054462-11-kunwu.chan@gmail.com \
--to=kunwu.chan@gmail.com \
--cc=boqun@kernel.org \
--cc=chentao@kylinos.cn \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--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 \
--cc=work@onurozkan.dev \
/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
all inboxes | Powered by JetHome®