From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Updates for v6.15
Date: Thu, 27 Mar 2025 22:13:57 +0900 [thread overview]
Message-ID: <20250327221357.bfa54d31c9f8b9b1e68ffe3d@kernel.org> (raw)
Hi Linus,
Probes updates for v6.15:
- probe-events: Add comments about entry data storing code to clarify
where and how the entry data is stored for function return events.
- probe-events: Log error for exceeding the number of arguments to help
user to identify error reason via tracefs/error_log file.
- selftests/ftrace: Improve the ftracetest to add followngs.
. Expand the tprobe event test to check if it can correctly find
the wrong format tracepoint name.
. Add new syntax error test to check whether error_log correctly
indicates a wrong character in the tracepoint name.
. Add a new dynamic events argument limitation test case which checks
max number of probe arguments.
Please pull the latest probes-v6.15 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v6.15
Tag SHA1: 395caaabf3068c20d718b981763bdfb0680be393
Head SHA1: bb9c6020f4c3a07a90dc36826cb5fbe83f09efd5
Masami Hiramatsu (Google) (5):
tracing: probe-events: Log error for exceeding the number of arguments
selftests/ftrace: Expand the tprobe event test to check wrong format
selftests/ftrace: Add new syntax error test
selftests/ftrace: Add dynamic events argument limitation test case
tracing: probe-events: Add comments about entry data storing code
----
kernel/trace/trace_eprobe.c | 2 ++
kernel/trace/trace_fprobe.c | 5 ++-
kernel/trace/trace_kprobe.c | 5 ++-
kernel/trace/trace_probe.c | 28 +++++++++++++++
kernel/trace/trace_probe.h | 1 +
kernel/trace/trace_uprobe.c | 9 +++--
.../ftrace/test.d/dynevent/add_remove_tprobe.tc | 14 ++++++++
.../ftrace/test.d/dynevent/dynevent_limitations.tc | 42 ++++++++++++++++++++++
.../ftrace/test.d/dynevent/fprobe_syntax_errors.tc | 1 +
9 files changed, 103 insertions(+), 4 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/dynevent/dynevent_limitations.tc
next reply other threads:[~2025-03-27 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 13:13 Masami Hiramatsu [this message]
2025-03-28 2:39 ` [GIT PULL] probes: Updates for v6.15 pr-tracker-bot
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=20250327221357.bfa54d31c9f8b9b1e68ffe3d@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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