From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Menglong Dong <menglong8.dong@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
jiang.biao@linux.dev, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] tracing/fprobe: Fix fprobe_ip_table related bugs
Date: Tue, 14 Apr 2026 10:19:12 +0900 [thread overview]
Message-ID: <20260414101912.c97d1248d34e35393e494e10@kernel.org> (raw)
In-Reply-To: <177606956628.929411.17392736689322577701.stgit@devnote2>
On Mon, 13 Apr 2026 17:39:26 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> Here is the 5th series of patches to fix bugs in fprobe.
> The previous version is here.
>
> https://lore.kernel.org/all/177584108931.388483.11311214679686745474.stgit@devnote2/
>
> This version fixes to remove fprobe_hash_node forcibly when fprobe
> registration failed [1/3] and skips updating ftrace_ops when fails
> to allocate memory in module unloading [2/3].
Hmm, Sashiko pointed out some issues in fprobe, which seems not introduced
this series but existing UAF cases.
https://sashiko.dev/#/patchset/177606956628.929411.17392736689322577701.stgit%40devnote2
Especially,
> In fprobe_return(), the code traverses the fprobe_table which contains
> RCU-protected struct fprobe_hlist nodes. These nodes are freed using
> kfree_rcu(hlist_array, rcu) in unregister_fprobe_nolock().
>
> To safely traverse this RCU-protected list, readers must hold the RCU read
> lock. However, fprobe_return() only calls preempt_disable_notrace(). While
> disabling preemption acts as an RCU-sched read-side critical section on
> non-RT kernels, it does not prevent regular RCU grace periods from
> completing on PREEMPT_RT. Thus, kfree_rcu() can free the hlist_array while
> fprobe_return() is actively iterating over it.
I would like to ask Steve a comment about this. Is fgraph return handler
context RCU safe?
Thanks,
>
> Thanks,
> ---
>
> Masami Hiramatsu (Google) (3):
> tracing/fprobe: Remove fprobe from hash in failure path
> tracing/fprobe: Avoid kcalloc() in rcu_read_lock section
> tracing/fprobe: Check the same type fprobe on table as the unregistered one
>
>
> kernel/trace/fprobe.c | 251 +++++++++++++++++++++++++++++--------------------
> 1 file changed, 147 insertions(+), 104 deletions(-)
>
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-04-14 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 8:39 [PATCH v5 0/3] tracing/fprobe: Fix fprobe_ip_table related bugs Masami Hiramatsu (Google)
2026-04-13 8:39 ` [PATCH v5 1/3] tracing/fprobe: Remove fprobe from hash in failure path Masami Hiramatsu (Google)
2026-04-13 8:39 ` [PATCH v5 2/3] tracing/fprobe: Avoid kcalloc() in rcu_read_lock section Masami Hiramatsu (Google)
2026-04-13 8:39 ` [PATCH v5 3/3] tracing/fprobe: Check the same type fprobe on table as the unregistered one Masami Hiramatsu (Google)
2026-04-14 1:19 ` Masami Hiramatsu [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=20260414101912.c97d1248d34e35393e494e10@kernel.org \
--to=mhiramat@kernel.org \
--cc=jiang.biao@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=menglong8.dong@gmail.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