From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
Rosen Penev <rosenp@gmail.com>,
Yash Suthar <yashsuthar983@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Updates for v7.2
Date: Tue, 16 Jun 2026 10:04:22 +0900 [thread overview]
Message-ID: <20260616100422.b25ab4aa9a977d04eda9ea96@kernel.org> (raw)
Hi Linus,
Probes updates for v7.2
- eprobes: BTF support for dereferencing pointers
. tracing/eprobes: Allow use of BTF names to dereference pointers. Add syntax
to the parsing of eprobes to typecast structure pointer trace event fields,
enabling BTF-based dereferencing instead of relying on manual offsets.
- probes: Improvements and robustness enhancements
. tracing: Use flexible array for entry fetch code. Store probe entry fetch
instructions in the probe_entry_arg allocation via a flexible array
member to simplify memory allocation and lifetime management.
. tracing: Replace BUG_ON with lockdep_assert_held in uprobe_buffer functions.
Replace BUG_ON() calls with lockdep_assert_held() in uprobe buffer
enable/disable paths to prevent kernel crashes and better verify lock ownership.
. tracing/probes: Ensure the uprobe buffer size is bigger than event size.
Add a BUILD_BUG_ON() assertion to guarantee that the per-CPU uprobe
working buffer size is always larger than the maximum probe event size.
Please pull the latest probes-v7.2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v7.2
Tag SHA1: ccffe554d710dba03357fc8d0c1f76ffc9d38f5b
Head SHA1: 69efd863a78584b9416ed6be0e1e7349124b4a00
Masami Hiramatsu (Google) (1):
tracing/probes: Ensure the uprobe buffer size is bigger than event size
Rosen Penev (1):
tracing: Use flexible array for entry fetch code
Steven Rostedt (1):
tracing/eprobes: Allow use of BTF names to dereference pointers
Yash Suthar (1):
tracing: Replace BUG_ON with lockdep_assert_held in uprobe_buffer functions
----
Documentation/trace/eprobetrace.rst | 4 +
kernel/trace/trace_probe.c | 181 +++++++++++++++++++++++++++++-------
kernel/trace/trace_probe.h | 7 +-
kernel/trace/trace_uprobe.c | 5 +-
4 files changed, 159 insertions(+), 38 deletions(-)
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next reply other threads:[~2026-06-16 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 1:04 Masami Hiramatsu [this message]
2026-06-16 12:36 ` 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=20260616100422.b25ab4aa9a977d04eda9ea96@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.org \
--cc=yashsuthar983@gmail.com \
/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
Powered by JetHome