From: Yonghong Song <yonghong.song@linux.dev>
To: Achill Gilgenast <fossdd@pwned.life>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Viktor Malik <vmalik@redhat.com>,
bpf@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] libbpf: avoid possible use of uninitialized mod_len
Date: Tue, 29 Jul 2025 09:17:34 -0700 [thread overview]
Message-ID: <49c6b3ba-7860-4b13-944f-5f503eb201fd@linux.dev> (raw)
In-Reply-To: <20250729094611.2065713-1-fossdd@pwned.life>
On 7/29/25 2:45 AM, Achill Gilgenast wrote:
> If not fn_name, mod_len does never get initialized which fails now with
> gcc15 on Alpine Linux edge:
>
> libbpf.c: In function 'find_kernel_btf_id.constprop':
> libbpf.c:10100:33: error: 'mod_len' may be used uninitialized [-Werror=maybe-uninitialized]
> 10100 | if (mod_name && strncmp(mod->name, mod_name, mod_len) != 0)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> libbpf.c:10070:21: note: 'mod_len' was declared here
> 10070 | int ret, i, mod_len;
> | ^~~~~~~
>
> Fixes: 8f8a024272f3 ("libbpf: support "module: Function" syntax for tracing programs")
> Signed-off-by: Achill Gilgenast <fossdd@pwned.life>
The code itself is actually okay. The error is triggered due to'maybe-uninitialized'.
To silence the compilation error, I think this change is okay.
Acked-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> tools/lib/bpf/libbpf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index e067cb5776bd..fb4d92c5c339 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -10086,27 +10086,27 @@ static int libbpf_find_prog_btf_id(const char *name, __u32 attach_prog_fd, int t
> btf__free(btf);
> if (err <= 0) {
> pr_warn("%s is not found in prog's BTF\n", name);
> goto out;
> }
> out:
> return err;
> }
>
> static int find_kernel_btf_id(struct bpf_object *obj, const char *attach_name,
> enum bpf_attach_type attach_type,
> int *btf_obj_fd, int *btf_type_id)
> {
> - int ret, i, mod_len;
> + int ret, i, mod_len = 0;
> const char *fn_name, *mod_name = NULL;
>
> fn_name = strchr(attach_name, ':');
> if (fn_name) {
> mod_name = attach_name;
> mod_len = fn_name - mod_name;
> fn_name++;
> }
>
> if (!mod_name || strncmp(mod_name, "vmlinux", mod_len) == 0) {
> ret = find_attach_btf_id(obj->btf_vmlinux,
> mod_name ? fn_name : attach_name,
> attach_type);
next prev parent reply other threads:[~2025-07-29 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 9:45 [PATCH] libbpf: avoid possible use of uninitialized mod_len Achill Gilgenast
2025-07-29 16:17 ` Yonghong Song [this message]
2025-07-30 16:13 ` Eduard Zingerman
2025-08-01 11:46 ` Achill Gilgenast
2025-08-01 12:04 ` Achill Gilgenast
2025-08-01 15:16 ` Alexei Starovoitov
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=49c6b3ba-7860-4b13-944f-5f503eb201fd@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=fossdd@pwned.life \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vmalik@redhat.com \
/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