linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org>,
	Peng Jiang <jiang.peng9@zte.com.cn>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Updates for v6.17
Date: Wed, 30 Jul 2025 17:49:46 +0900	[thread overview]
Message-ID: <20250730174946.6c21cafc03bd295c58cc149f@kernel.org> (raw)

Linus,

Probes updates for v6.17:

 - Stack usage reduction for probe events:
   - Allocate string buffers from the heap for uprobe, eprobe, kprobe,
     and fprobe events to avoid stack overflow.
   - Allocate traceprobe_parse_context from the heap to prevent
     potential stack overflow.
   - Fix a typo in the above commit.

 - New features for eprobe and tprobe events:
   - Add support for arrays in eprobes.
   - Support multiple tprobes on the same tracepoint.

 - Improve efficiency:
   - Register fprobe-events only when it is enabled to reduce overhead.
   - Register tracepoints for tprobe events only when enabled to
     resolve a lock dependency.

 - Code Cleanup:
   - Add kerneldoc for traceprobe_parse_event_name() and __get_insn_slot().
   - Sort #include alphabetically in the probes code.
   - Remove the unused 'mod' field from the tprobe-event.
   - Clean up the entry-arg storing code in probe-events.

 - Selftest update
   - Enable fprobe events before checking enable_functions in selftests.


Please pull the latest probes-v6.17 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v6.17

Tag SHA1: 04ecc3e4ee6e6163c07baeec62ffbff04fd8ae09
Head SHA1: 133c302a0c60bca1f0a2f5f85ef11e7f5e8f1331


Masami Hiramatsu (Google) (14):
      tracing: probe-events: Cleanup entry-arg storing code
      tracing: tprobe-events: Remove mod field from tprobe-event
      tracing: tprobe-events: Support multiple tprobes on the same tracepoint
      tracing: fprobe-events: Register fprobe-events only when it is enabled
      selftests: tracing: Enable fprobe events before checking enable_functions
      tracing: tprobe-events: Register tracepoint when enable tprobe event
      tracing: probes: Sort #include alphabetically
      tracing: probe: Allocate traceprobe_parse_context from heap
      tracing: fprobe-event: Allocate string buffers from heap
      tracing: kprobe-event: Allocate string buffers from heap
      tracing: eprobe-event: Allocate string buffers from heap
      tracing: uprobe-event: Allocate string buffers from heap
      tracing: probes: Add a kerneldoc for traceprobe_parse_event_name()
      tracing: trace_fprobe: Fix typo of the semicolon

Peng Jiang (1):
      kprobes: Add missing kerneldoc for __get_insn_slot

Steven Rostedt (1):
      tracing: Have eprobes handle arrays

----
 include/linux/fprobe.h                             |   5 +
 include/linux/module.h                             |   4 +
 kernel/kprobes.c                                   |   8 +-
 kernel/trace/fprobe.c                              |   5 +
 kernel/trace/trace_eprobe.c                        |  53 +-
 kernel/trace/trace_fprobe.c                        | 614 ++++++++++++++-------
 kernel/trace/trace_kprobe.c                        |  57 +-
 kernel/trace/trace_probe.c                         | 150 +++--
 kernel/trace/trace_probe.h                         |  26 +-
 kernel/trace/trace_uprobe.c                        |  53 +-
 .../ftrace/test.d/dynevent/add_remove_fprobe.tc    |  30 +-
 11 files changed, 664 insertions(+), 341 deletions(-)

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

             reply	other threads:[~2025-07-30  8:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  8:49 Masami Hiramatsu [this message]
2025-07-31  0:35 ` [GIT PULL] probes: Updates for v6.17 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=20250730174946.6c21cafc03bd295c58cc149f@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=jiang.peng9@zte.com.cn \
    --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;
as well as URLs for NNTP newsgroup(s).