public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Martin Kaiser <martin@kaiser.cx>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Updates for v7.1
Date: Fri, 17 Apr 2026 10:05:43 +0900	[thread overview]
Message-ID: <20260417100543.1f96ba198e7bd99abc0ddbe1@kernel.org> (raw)

Hi Linus,

Probes updates for v7.1

- fprobe: do not zero out unused fgraph_data. This removes unneeded
  memset of fgraph_data in fprobe entry handler.


Please pull the latest probes-v7.1 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
probes-v7.1

Tag SHA1: bf593fe216d8bf264b53e0235145363623bc92f0
Head SHA1: e0a384434ae1bdfb03954c46c464e3dbd3223ad6


Martin Kaiser (1):
      tracing: fprobe: do not zero out unused fgraph_data

----
 kernel/trace/fprobe.c | 2 --
 1 file changed, 2 deletions(-)
---------------------------
commit e0a384434ae1bdfb03954c46c464e3dbd3223ad6
Author: Martin Kaiser <martin@kaiser.cx>
Date:   Wed Mar 25 00:47:01 2026 +0900

    tracing: fprobe: do not zero out unused fgraph_data
    
    If fprobe_entry does not fill the allocated fgraph_data completely, the
    unused part does not have to be zeroed.
    
    fgraph_data is a short-lived part of the shadow stack. The preceding
    length field allows locating the end regardless of the content.
    
    Link: https://lore.kernel.org/all/20260324084804.375764-1-martin@kaiser.cx/
    
    Signed-off-by: Martin Kaiser <martin@kaiser.cx>
    Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

diff --git a/kernel/trace/fprobe.c b/kernel/trace/fprobe.c
index dcadf1d23b8a..56d145017902 100644
--- a/kernel/trace/fprobe.c
+++ b/kernel/trace/fprobe.c
@@ -450,8 +450,6 @@ static int fprobe_fgraph_entry(struct ftrace_graph_ent *trace, struct fgraph_ops
 				used += FPROBE_HEADER_SIZE_IN_LONG + size_words;
 		}
 	}
-	if (used < reserved_words)
-		memset(fgraph_data + used, 0, reserved_words - used);
 
 	/* If any exit_handler is set, data must be used. */
 	return used != 0;


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

             reply	other threads:[~2026-04-17  1:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  1:05 Masami Hiramatsu [this message]
2026-04-17 17:50 ` [GIT PULL] probes: Updates for v7.1 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=20260417100543.1f96ba198e7bd99abc0ddbe1@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@kaiser.cx \
    --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