mirror of https://lore.kernel.org/lkml/
 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>,
	Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] probes: Fixes for v7.1-rc6
Date: Fri, 5 Jun 2026 22:48:28 +0900	[thread overview]
Message-ID: <20260605224828.df356b24f771ac7db16b9045@kernel.org> (raw)

Linus,

Probes fixes for v7.1-rc6

- tracing/probes: Point the error offset correctly for eprobe argument error
  Fix the eprobe event parser to point error position correctly.


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


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

Tag SHA1: 504a88cae60802a3c55eb5e8c2ae67ab641757d1
Head SHA1: 85e0f27dd1396307913ffc5745b0c05137e9beac


Masami Hiramatsu (Google) (1):
      tracing/probes: Point the error offset correctly for eprobe argument error

----
 kernel/trace/trace_probe.c                                              | 2 --
 tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc | 2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)
---------------------------
commit 85e0f27dd1396307913ffc5745b0c05137e9beac
Author: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Date:   Mon May 25 11:21:14 2026 +0900

    tracing/probes: Point the error offset correctly for eprobe argument error
    
    Fix to point the error offset correctly for eprobe argument error.
    In the cleanup commit 1b8b0cd754cd ("tracing/probes: Move event parameter
    fetching code to common parser"), due to incorrect backward compatibility
    aimed at conforming to the test specifications, the error location was set
    to 0 when a non-existent formal parameter was specified for Eprobe.
    However, this should be corrected in both the test and the implementation
    to point correct error position.
    
    Link: https://lore.kernel.org/all/177967567399.209006.1451571244515632097.stgit@devnote2/
    
    Fixes: 1b8b0cd754cd ("tracing/probes: Move event parameter fetching code to common parser")
    Cc: stable@vger.kernel.org
    Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
    Reviewed-by: Steven Rostedt <rostedt@goodmis.org>

diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
index e0d3a0da26af..44c22d4e7881 100644
--- a/kernel/trace/trace_probe.c
+++ b/kernel/trace/trace_probe.c
@@ -962,8 +962,6 @@ static int parse_probe_vars(char *orig_arg, const struct fetch_type *t,
 			code->op = FETCH_OP_COMM;
 			return 0;
 		}
-		/* backward compatibility */
-		ctx->offset = 0;
 		goto inval;
 	}
 
diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc b/tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc
index 4f5e8c665156..2a680c086047 100644
--- a/tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc
+++ b/tools/testing/selftests/ftrace/test.d/dynevent/eprobes_syntax_errors.tc
@@ -20,7 +20,7 @@ check_error 'e:foo/^123456789012345678901234567890123456789012345678901234567890
 check_error 'e:foo/^bar.1 syscalls/sys_enter_openat'	# BAD_EVENT_NAME
 
 check_error 'e:foo/bar syscalls/sys_enter_openat arg=^dfd'	# BAD_FETCH_ARG
-check_error 'e:foo/bar syscalls/sys_enter_openat ^arg=$foo'	# BAD_ATTACH_ARG
+check_error 'e:foo/bar syscalls/sys_enter_openat arg=^$foo'	# BAD_ATTACH_ARG
 
 if grep -q '<attached-group>\.<attached-event>.*\[if <filter>\]' README; then
   check_error 'e:foo/bar syscalls/sys_enter_openat if ^'	# NO_EP_FILTER

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

             reply	other threads:[~2026-06-05 13:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 13:48 Masami Hiramatsu [this message]
2026-06-05 18: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=20260605224828.df356b24f771ac7db16b9045@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

all inboxes | Powered by JetHome®