public inbox for linux-kselftest@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 0/3] Support comma-separated symbols and :entry/:exit
Date: Thu, 27 Nov 2025 15:12:18 +0900	[thread overview]
Message-ID: <20251127151218.4763b25c751bb2aac4b1ee36@kernel.org> (raw)
In-Reply-To: <20251126184110.72241-1-seokwoo.chung130@gmail.com>

On Wed, 26 Nov 2025 13:41:07 -0500
"Seokwoo Chung (Ryan)" <seokwoo.chung130@gmail.com> wrote:

> Extend fprobe to support list-style filters and explicit entry/exit suffixes.
> Currentyl, fprobe only supports a single symbol (or wildcard) per event.
> This patch allows users to specify a comma-separated list of symbols.
> 
> New Syntax:
> - f:[GRP/][EVENT] func1,func2,func3:entry
> - f:[GRP/][EVENT] func1,func2,func3:exit

Thanks for updating!

> 
> Logic changes:
> - Refactor parsing logic into 'parse_fprobe_spec'
> - Support '!' prefix for exclusion
> - Disable BTF lookup ('ctx->funcname = NULL') when a list or wildcard is used,
>   as a single function signature cannot apply to multiple functions.
> - Reject legacy '%return' suffix when used with lists or wildcards
> - Update tracefs/README
> 
> Testing:
> Verified on x86_64 via QEMU. Checked registration of lists, exclusions, and
> explicit suffixes. Verified rejection of invalid syntax including trailing
> commas and mixed legacy/new syntax.
> 
> Seokwoo Chung (Ryan) (3):
>   docs: tracing/fprobe: Document list filters and :entry/:exit
>   tracing/fprobe: Support comma-separated symbols and :entry/:exit

For the next time, please add docs patch after code change because of bisect.
(Or, include the document update into code update.)

>   selftests/ftrace: Add accept cases for fprobe list syntax

Testing after code is good. :)

Thank you,

> 
> Changes in v4:
> - Added validation to reject trailing commas (empty tokens) in symbol lists
> - Added vaildation to reject mixed of list syntax with %return suffix
> - Refactored parse_fprobe_spec to user __free(kfree) for automatic memory
>   cleanup
> - Removed the now-unused parse_symbol_and_return function to avoid compiler
>   warnings.
> - Tigtened %return detection to ensure it only matches as a strict suffix, not a
>   substring
> - Link to v3: https://lore.kernel.org/lkml/20250904103219.f4937968362bfff1ecd3f004@kernel.org/
> 
>  Documentation/trace/fprobetrace.rst           |  17 +-
>  kernel/trace/trace.c                          |   3 +-
>  kernel/trace/trace_fprobe.c                   | 209 ++++++++++++++----
>  .../ftrace/test.d/dynevent/fprobe_list.tc     |  92 ++++++++
>  4 files changed, 269 insertions(+), 52 deletions(-)
>  create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/fprobe_list.tc
> 
> -- 
> 2.43.0
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  parent reply	other threads:[~2025-11-27  6:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 18:41 [PATCH v4 0/3] Support comma-separated symbols and :entry/:exit Seokwoo Chung (Ryan)
2025-11-26 18:41 ` [PATCH v4 1/3] docs: tracing/fprobe: Document list filters " Seokwoo Chung (Ryan)
2025-11-26 18:41 ` [PATCH v4 2/3] tracing/fprobe: Support comma-separated symbols " Seokwoo Chung (Ryan)
2025-11-27  6:11   ` Masami Hiramatsu
2025-11-27 12:12   ` kernel test robot
2025-11-27 14:49   ` kernel test robot
2025-11-27 15:00   ` kernel test robot
2026-01-15 11:07   ` kernel test robot
2026-01-15 11:17   ` kernel test robot
2025-11-26 18:41 ` [PATCH v4 3/3] selftests/ftrace: Add accept cases for fprobe list syntax Seokwoo Chung (Ryan)
2025-11-27  6:12 ` Masami Hiramatsu [this message]
2026-01-14 22:12 ` [PATCH v5 0/3] tracing/fprobe: Support comma-separated symbols and :entry/:exit Seokwoo Chung (Ryan)
2026-01-14 22:13 ` Seokwoo Chung (Ryan)
2026-01-14 22:13   ` [PATCH v5 1/3] " Seokwoo Chung (Ryan)
2026-01-20 20:50     ` Steven Rostedt
2026-01-20 20:52       ` Steven Rostedt
2026-01-14 22:13   ` [PATCH v5 2/3] docs: tracing/fprobe: Document list filters " Seokwoo Chung (Ryan)
2026-01-20 20:51     ` Steven Rostedt
2026-01-14 22:13   ` [PATCH v5 3/3] selftests/ftrace: Add accept cases for fprobe list syntax Seokwoo Chung (Ryan)
2026-01-20 20:51     ` Steven Rostedt

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=20251127151218.4763b25c751bb2aac4b1ee36@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