public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 0/3] tracing/fprobe: Fix fprobe_ip_table related bugs
Date: Sat, 11 Apr 2026 02:11:29 +0900	[thread overview]
Message-ID: <177584108931.388483.11311214679686745474.stgit@devnote2> (raw)

Here are patches to fix bugs in fprobe.

The previous version is here.

https://lore.kernel.org/all/177581370903.617881.3002655215679528157.stgit@mhiramat.tok.corp.google.com/

In this version, I fixed some issues on the previous version.

Patch 1/3 updates:
      - Remove short-cut case because we always need to upadte ftrace_ops.
      - Use guard(mutex) in register_fprobe_ips() to unlock it correctly.
      - Remove redundant !ret check in register_fprobe_ips().
      - Do not set hlist_array->size in failure case, instead,
        hlist_array->array[i].fp is set only when insertion is succeeded.
Patch 2/3 updates:
      - fix a build error typo in case of CONFIG_DYNAMIC_FTRACE=n.

Thank you!


---

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 |  236 ++++++++++++++++++++++++++++---------------------
 1 file changed, 135 insertions(+), 101 deletions(-)

--
Signature

             reply	other threads:[~2026-04-10 17:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 17:11 Masami Hiramatsu (Google) [this message]
2026-04-10 17:11 ` [PATCH v4 1/3] tracing/fprobe: Remove fprobe from hash in failure path Masami Hiramatsu (Google)
2026-04-10 17:11 ` [PATCH v4 2/3] tracing/fprobe: Avoid kcalloc() in rcu_read_lock section Masami Hiramatsu (Google)
2026-04-10 17:11 ` [PATCH v4 3/3] tracing/fprobe: Check the same type fprobe on table as the unregistered one Masami Hiramatsu (Google)

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=177584108931.388483.11311214679686745474.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