From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chen Jun <chenjun102@huawei.com>
Subject: [PATCH v2 0/2] tracing: Add 'within' filter logic
Date: Fri, 21 Aug 2026 19:28:20 -0400 [thread overview]
Message-ID: <20260821232820.717143516@kernel.org> (raw)
Add a "within" filter predicate that tests whether a given function
appears in the current call stack at event time. The function name
is resolved to its address range via kallsyms during filter setup;
at runtime, stack_trace_save() captures the call stack and compares
each return address against the stored range.
Changes since v1: https://lore.kernel.org/linux-trace-kernel/20260608145556.94931-1-chenjun102@huawei.com
- Added patch to show error message
Chen Jun (1):
tracing: Add "within" filter for call-stack-based event filtering
Steven Rostedt (1):
tracnig: Add proper error message for glob use with "within" filter
----
Documentation/trace/events.rst | 12 +++++++++++
include/linux/trace_events.h | 1 +
kernel/trace/trace.h | 3 ++-
kernel/trace/trace_events.c | 3 +++
kernel/trace/trace_events_filter.c | 44 ++++++++++++++++++++++++++++++++++++--
5 files changed, 60 insertions(+), 3 deletions(-)
next reply other threads:[~2026-08-21 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 23:28 Steven Rostedt [this message]
2026-08-21 23:28 ` [PATCH v2 1/2] tracing: Add "within" filter for call-stack-based event filtering Steven Rostedt
2026-08-21 23:28 ` [PATCH v2 2/2] tracnig: Add proper error message for glob use with "within" filter 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=20260821232820.717143516@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chenjun102@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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