From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Seokwoo Chung (Ryan)" <seokwoo.chung130@gmail.com>
Cc: rostedt@goodmis.org, corbet@lwn.net, shuah@kernel.org,
mathieu.desnoyers@efficios.com, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 0/4] tracing/fprobe: Support comma-separated symbol lists and :entry/:exit suffixes
Date: Tue, 24 Mar 2026 10:51:33 +0900 [thread overview]
Message-ID: <20260324105133.aeddf1a049afead53f92cc2c@kernel.org> (raw)
In-Reply-To: <20260205135842.20517-1-seokwoo.chung130@gmail.com>
Hi,
Sorry, I completely missed this series. Let me review it.
Thank you,
On Thu, 5 Feb 2026 08:58:38 -0500
"Seokwoo Chung (Ryan)" <seokwoo.chung130@gmail.com> wrote:
> Extend the fprobe event interface to accept comma-separated symbol lists
> with ! exclusion prefix, and :entry/:exit suffixes as an alternative to
> %return. Single-symbol probes retain full backward compatibility with
> %return.
>
> Example usage:
> f:mygroup/myevent vfs_read,!vfs_write,vfs_open:entry
> f:mygroup/myexit vfs_read,vfs_open:exit
>
> Changes since v5:
> - Fix missing closing brace in the empty-token check that caused a
> build error.
> - Remove redundant strchr/strstr checks for tracepoint validation;
> the character validation loop already rejects ',', ':', and '%'.
> - Add trace_probe_log_err() to the tracepoint character validation
> loop so users see what went wrong in tracefs/error_log (reviewer
> feedback from Masami Hiramatsu).
> - Remove unnecessary braces around single-statement if per kernel
> coding style (reviewer feedback).
> - Extract list parsing into parse_fprobe_list() to keep
> parse_fprobe_spec() focused (reviewer feedback).
> - New patch 2/4: add glob_match_comma_list() in kernel/trace/fprobe.c
> so register_fprobe() correctly handles comma-separated filter
> strings. Without this, enabling a list-mode fprobe event failed
> with "Could not enable event" because glob_match() does not
> understand commas.
> - Reorder: documentation patch now comes after all code changes.
> - Updated selftest commit message to note that existing tests
> (add_remove_fprobe.tc, fprobe_syntax_errors.tc,
> add_remove_fprobe_repeat.tc) report UNSUPPORTED because their
> "requires" lines still check for the old %return syntax in README.
> Their requires lines need updating in a follow-up patch.
>
> Tested in QEMU/KVM but I am not too confident if I configured correctly and
> would like to ask for further testing.
>
> Seokwoo Chung (Ryan) (4):
> tracing/fprobe: Support comma-separated symbols and :entry/:exit
> fprobe: Support comma-separated filters in register_fprobe()
> docs: tracing/fprobe: Document list filters and :entry/:exit
> selftests/ftrace: Add accept cases for fprobe list syntax
>
> Documentation/trace/fprobetrace.rst | 17 +-
> kernel/trace/fprobe.c | 30 ++-
> kernel/trace/trace.c | 3 +-
> kernel/trace/trace_fprobe.c | 219 ++++++++++++++----
> .../ftrace/test.d/dynevent/fprobe_list.tc | 92 ++++++++
> 5 files changed, 308 insertions(+), 53 deletions(-)
> create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/fprobe_list.tc
>
> --
> 2.43.0
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-03-24 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 13:58 [PATCH v6 0/4] tracing/fprobe: Support comma-separated symbol lists and :entry/:exit suffixes Seokwoo Chung (Ryan)
2026-02-05 13:58 ` [PATCH v6 1/4] tracing/fprobe: Support comma-separated symbols and :entry/:exit Seokwoo Chung (Ryan)
2026-03-24 1:50 ` Masami Hiramatsu
2026-02-05 13:58 ` [PATCH v6 2/4] fprobe: Support comma-separated filters in register_fprobe() Seokwoo Chung (Ryan)
2026-03-24 1:59 ` Masami Hiramatsu
2026-02-05 13:58 ` [PATCH v6 3/4] docs: tracing/fprobe: Document list filters and :entry/:exit Seokwoo Chung (Ryan)
2026-03-24 4:07 ` Masami Hiramatsu
2026-02-05 13:58 ` [PATCH v6 4/4] selftests/ftrace: Add accept cases for fprobe list syntax Seokwoo Chung (Ryan)
2026-03-24 4:12 ` Masami Hiramatsu
2026-03-24 1:51 ` 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=20260324105133.aeddf1a049afead53f92cc2c@kernel.org \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=seokwoo.chung130@gmail.com \
--cc=shuah@kernel.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