From: "Markus Schneider-Pargmann" <msp@baylibre.com>
To: "Martin Kaiser" <martin@kaiser.cx>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>
Cc: "Markus Schneider-Pargmann" <msp@baylibre.com>,
<linux-trace-kernel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tracing: probes: remove unused variable
Date: Mon, 04 May 2026 10:59:10 +0200 [thread overview]
Message-ID: <DI9ROQRRXZJI.3MUR7JAFEB02C@baylibre.com> (raw)
In-Reply-To: <20260502135826.146257-1-martin@kaiser.cx>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
On Sat May 2, 2026 at 3:57 PM CEST, Martin Kaiser wrote:
> params is always NULL in traceprobe_expand_meta_args, it can be removed.
>
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
Reviewed-by: Markus Schneider-Pargmann (The Capable Hub) <msp@baylibre.com>
Best
Markus
> ---
> Would it be better to return ERR_PTR(-EOPNOTSUPP) instead of NULL, similar to
> what is done in other places where NOSUP_BTFARG is logged? This would make the
> parsing fail if $arg* is used without BTF support. At the moment, we skip the
> $arg*...
>
> kernel/trace/trace_probe.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> index e0d3a0da26af..b627093a941e 100644
> --- a/kernel/trace/trace_probe.c
> +++ b/kernel/trace/trace_probe.c
> @@ -1729,7 +1729,6 @@ const char **traceprobe_expand_meta_args(int argc, const char *argv[],
> int *new_argc, char *buf, int bufsize,
> struct traceprobe_parse_context *ctx)
> {
> - const struct btf_param *params = NULL;
> int i, j, n, used, ret, args_idx = -1;
> const char **new_argv __free(kfree) = NULL;
>
> @@ -1747,7 +1746,7 @@ const char **traceprobe_expand_meta_args(int argc, const char *argv[],
> if (args_idx != -1) {
> /* $arg* requires BTF info */
> trace_probe_log_err(0, NOSUP_BTFARG);
> - return (const char **)params;
> + return NULL;
> }
> *new_argc = argc;
> return NULL;
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 289 bytes --]
next prev parent reply other threads:[~2026-05-04 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 13:57 [PATCH] tracing: probes: remove unused variable Martin Kaiser
2026-05-04 8:59 ` Markus Schneider-Pargmann [this message]
2026-10-13 9:17 ` Masami Hiramatsu
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=DI9ROQRRXZJI.3MUR7JAFEB02C@baylibre.com \
--to=msp@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.