From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v8 01/10] tracing/probes: Make the $ prefix mandatory for comm access
Date: Thu, 25 Jun 2026 08:33:38 +0900 [thread overview]
Message-ID: <20260625083338.60b38483b5766c841ce4af32@kernel.org> (raw)
In-Reply-To: <178231209724.732967.12049805699091810641.stgit@devnote2>
On Wed, 24 Jun 2026 23:41:37 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Since $comm or $COMM are not event field but special fetcharg
> variables to access current->comm, It should not be accessed
> without '$' prefix even with typecast.
>
Let me pick this to probes/core.
Thanks,
> Fixes: 69efd863a785 ("tracing/eprobes: Allow use of BTF names to dereference pointers")
> Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> ---
> Changes in v8:
> - Newly added.
> ---
> kernel/trace/trace_probe.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> index c10bbb0df7b9..0da7c0b53ba7 100644
> --- a/kernel/trace/trace_probe.c
> +++ b/kernel/trace/trace_probe.c
> @@ -342,10 +342,6 @@ static int parse_trace_event(char *arg, struct fetch_insn *code,
> ret = parse_trace_event_arg(arg, code, ctx);
> if (!ret)
> return 0;
> - if (strcmp(arg, "comm") == 0 || strcmp(arg, "COMM") == 0) {
> - code->op = FETCH_OP_COMM;
> - return 0;
> - }
> return -EINVAL;
> }
>
> @@ -1065,8 +1061,14 @@ static int parse_probe_vars(char *orig_arg, const struct fetch_type *t,
> int len;
>
> if (ctx->flags & TPARG_FL_TEVENT) {
> - if (parse_trace_event(arg, code, ctx) < 0)
> + if (parse_trace_event(arg, code, ctx) < 0) {
> + /* 'comm' should be checked after field parsing. */
> + if (strcmp(arg, "comm") == 0 || strcmp(arg, "COMM") == 0) {
> + code->op = FETCH_OP_COMM;
> + return 0;
> + }
> goto inval;
> + }
> return 0;
> }
>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-06-24 23:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 14:41 [PATCH v8 00/10] tracing/probes: Add more typecast features Masami Hiramatsu (Google)
2026-06-24 14:41 ` [PATCH v8 01/10] tracing/probes: Make the $ prefix mandatory for comm access Masami Hiramatsu (Google)
2026-06-24 23:33 ` Masami Hiramatsu [this message]
2026-06-24 14:41 ` [PATCH v8 02/10] tracing/probes: Allow eprobe to use variable without $ prefix Masami Hiramatsu (Google)
2026-06-24 14:41 ` [PATCH v8 03/10] tracing/probes: Support dumping fetcharg program for debugging dynamic events Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 04/10] tracing/probes: Support typecast for various probe events Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 05/10] tracing/probes: Support nested typecast Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 06/10] tracing/probes: Type casting always involves nested calls Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 07/10] tracing/probes: Support field specifier option for typecast Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 08/10] tracing/probes: Add $current variable support Masami Hiramatsu (Google)
2026-06-24 14:42 ` [PATCH v8 09/10] tracing/probes: Add this_cpu_read() and this_cpu_ptr() dereference method to fetcharg Masami Hiramatsu (Google)
2026-06-24 14:43 ` [PATCH v8 10/10] tracing/probes: Add a new testcase for BTF typecasts Masami Hiramatsu (Google)
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=20260625083338.60b38483b5766c841ce4af32@kernel.org \
--to=mhiramat@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.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