From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Menglong Dong <dongml2@chinatelecom.cn>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] tracing: fprobe: fix suspicious rcu usage in fprobe_entry
Date: Mon, 1 Sep 2025 17:22:31 +0900 [thread overview]
Message-ID: <20250901172231.67db79e4bc5652ac15c32224@kernel.org> (raw)
In-Reply-To: <20250829021436.19982-1-dongml2@chinatelecom.cn>
On Fri, 29 Aug 2025 10:14:36 +0800
Menglong Dong <dongml2@chinatelecom.cn> wrote:
> rcu_read_lock() is not needed in fprobe_entry, but rcu_dereference_check()
> is used in rhltable_lookup(), which causes suspicious RCU usage warning:
>
> WARNING: suspicious RCU usage
> 6.17.0-rc1-00001-gdfe0d675df82 #1 Tainted: G S
> -----------------------------
> include/linux/rhashtable.h:602 suspicious rcu_dereference_check() usage!
> ......
> stack backtrace:
> CPU: 1 UID: 0 PID: 4652 Comm: ftracetest Tainted: G S
> Tainted: [S]=CPU_OUT_OF_SPEC, [I]=FIRMWARE_WORKAROUND
> Hardware name: Dell Inc. OptiPlex 7040/0Y7WYT, BIOS 1.1.1 10/07/2015
> Call Trace:
> <TASK>
> dump_stack_lvl+0x7c/0x90
> lockdep_rcu_suspicious+0x14f/0x1c0
> __rhashtable_lookup+0x1e0/0x260
> ? __pfx_kernel_clone+0x10/0x10
> fprobe_entry+0x9a/0x450
> ? __lock_acquire+0x6b0/0xca0
> ? find_held_lock+0x2b/0x80
> ? __pfx_fprobe_entry+0x10/0x10
> ? __pfx_kernel_clone+0x10/0x10
> ? lock_acquire+0x14c/0x2d0
> ? __might_fault+0x74/0xc0
> function_graph_enter_regs+0x2a0/0x550
> ? __do_sys_clone+0xb5/0x100
> ? __pfx_function_graph_enter_regs+0x10/0x10
> ? _copy_to_user+0x58/0x70
> ? __pfx_kernel_clone+0x10/0x10
> ? __x64_sys_rt_sigprocmask+0x114/0x180
> ? __pfx___x64_sys_rt_sigprocmask+0x10/0x10
> ? __pfx_kernel_clone+0x10/0x10
> ftrace_graph_func+0x87/0xb0
>
> Fix this by using rcu_read_lock() for rhltable_lookup(). Alternatively, we
> can use rcu_lock_acquire(&rcu_lock_map) here to obtain better performance.
Yeah, that kind of trick may not good.
> However, it's not a common usage :/
>
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202508281655.54c87330-lkp@intel.com
> Fixes: dfe0d675df82 ("tracing: fprobe: use rhltable for fprobe_ip_table")
> Signed-off-by: Menglong Dong <dongml2@chinatelecom.cn>
OK, I agree this fixes the problem. Let me pick it.
> ---
> kernel/trace/fprobe.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
> index fb127fa95f21..fece0f849c1c 100644
> --- a/kernel/trace/fprobe.c
> +++ b/kernel/trace/fprobe.c
> @@ -269,7 +269,9 @@ static int fprobe_entry(struct ftrace_graph_ent *trace, struct fgraph_ops *gops,
> if (WARN_ON_ONCE(!fregs))
> return 0;
>
> + rcu_read_lock();
> head = rhltable_lookup(&fprobe_ip_table, &func, fprobe_rht_params);
> + rcu_read_unlock();
> reserved_words = 0;
> rhl_for_each_entry_rcu(node, pos, head, hlist) {
> if (node->addr != func)
> --
> 2.51.0
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-09-01 8:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 2:14 Menglong Dong
2025-08-29 2:23 ` Steven Rostedt
2025-08-29 2:49 ` menglong.dong
2025-08-29 11:12 ` Paul E. McKenney
2025-08-29 11:11 ` Paul E. McKenney
2025-09-01 8:06 ` Masami Hiramatsu
2025-09-01 15:00 ` Paul E. McKenney
2025-09-02 6:59 ` Masami Hiramatsu
2025-09-02 11:58 ` Paul E. McKenney
2025-09-03 9:43 ` Herbert Xu
2025-09-04 9:44 ` [PATCH] rhashtable: Use rcu_dereference_all and rcu_dereference_all_check Herbert Xu
2025-09-08 15:23 ` Paul E. McKenney
2025-09-09 9:50 ` [v2 PATCH] " Herbert Xu
2025-09-25 10:17 ` Andrea Righi
2025-09-01 10:06 ` [PATCH] tracing: fprobe: fix suspicious rcu usage in fprobe_entry Herbert Xu
2025-09-01 8:22 ` Masami Hiramatsu [this message]
2025-09-02 9:17 ` Herbert Xu
2025-09-02 9:50 ` menglong.dong
2025-09-03 4:22 ` Herbert Xu
2025-09-04 3:37 ` Menglong Dong
2025-09-04 4:29 ` Masami Hiramatsu
2025-09-04 5:42 ` Menglong Dong
2025-09-04 9:08 ` Herbert Xu
2025-09-02 14:57 ` Steven Rostedt
2025-09-03 4:23 ` Herbert Xu
2025-09-04 5:41 ` menglong.dong
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=20250901172231.67db79e4bc5652ac15c32224@kernel.org \
--to=mhiramat@kernel.org \
--cc=dongml2@chinatelecom.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=oliver.sang@intel.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®