From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
llvm@lists.linux.dev, stable@vger.kernel.org
Subject: Re: [PATCH] tracing/probes: Avoid using params uninitialized in parse_btf_arg()
Date: Wed, 16 Jul 2025 13:16:54 +0900 [thread overview]
Message-ID: <20250716131654.93b969d6eab59b0cd292a3f3@kernel.org> (raw)
In-Reply-To: <20250715-trace_probe-fix-const-uninit-warning-v1-1-98960f91dd04@kernel.org>
On Tue, 15 Jul 2025 20:19:44 -0700
Nathan Chancellor <nathan@kernel.org> wrote:
> After a recent change in clang to strengthen uninitialized warnings [1],
> it points out that in one of the error paths in parse_btf_arg(), params
> is used uninitialized:
>
> kernel/trace/trace_probe.c:660:19: warning: variable 'params' is uninitialized when used here [-Wuninitialized]
> 660 | return PTR_ERR(params);
> | ^~~~~~
>
> Match many other NO_BTF_ENTRY error cases and return -ENOENT, clearing
> up the warning.
Good catch! let me pick this up.
Thank you,
>
> Cc: stable@vger.kernel.org
> Closes: https://github.com/ClangBuiltLinux/linux/issues/2110
> Fixes: d157d7694460 ("tracing/probes: Support BTF field access from $retval")
> Link: https://github.com/llvm/llvm-project/commit/2464313eef01c5b1edf0eccf57a32cdee01472c7 [1]
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> ---
> kernel/trace/trace_probe.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace_probe.c b/kernel/trace/trace_probe.c
> index 424751cdf31f..40830a3ecd96 100644
> --- a/kernel/trace/trace_probe.c
> +++ b/kernel/trace/trace_probe.c
> @@ -657,7 +657,7 @@ static int parse_btf_arg(char *varname,
> ret = query_btf_context(ctx);
> if (ret < 0 || ctx->nr_params == 0) {
> trace_probe_log_err(ctx->offset, NO_BTF_ENTRY);
> - return PTR_ERR(params);
> + return -ENOENT;
> }
> }
> params = ctx->params;
>
> ---
> base-commit: 6921d1e07cb5eddec830801087b419194fde0803
> change-id: 20250715-trace_probe-fix-const-uninit-warning-7dc3accce903
>
> Best regards,
> --
> Nathan Chancellor <nathan@kernel.org>
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-07-16 4:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 3:19 [PATCH] tracing/probes: Avoid using params uninitialized in parse_btf_arg() Nathan Chancellor
2025-07-16 4:16 ` Masami Hiramatsu [this message]
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=20250716131654.93b969d6eab59b0cd292a3f3@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mathieu.desnoyers@efficios.com \
--cc=nathan@kernel.org \
--cc=rostedt@goodmis.org \
--cc=stable@vger.kernel.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).