From: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: 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: [PATCH v5 0/3] tracing/fprobe: Fix fprobe_ip_table related bugs
Date: Mon, 13 Apr 2026 17:39:26 +0900 [thread overview]
Message-ID: <177606956628.929411.17392736689322577701.stgit@devnote2> (raw)
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].
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>
next reply other threads:[~2026-04-13 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 8:39 Masami Hiramatsu (Google) [this message]
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 ` [PATCH v5 0/3] tracing/fprobe: Fix fprobe_ip_table related bugs Masami Hiramatsu
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=177606956628.929411.17392736689322577701.stgit@devnote2 \
--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