Re: [PATCH] libbpf: avoid possible use of uninitialized mod_len

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 1, 2025 at 5:05 AM Achill Gilgenast <fossdd@xxxxxxxxxx> wrote:
>
> On Fri Aug 1, 2025 at 1:46 PM CEST, 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;
> >             |                     ^~~~~~~
> >
> > Signed-off-by: Achill Gilgenast <fossdd@xxxxxxxxxx>
> > Acked-by: Yonghong Song <yonghong.song@xxxxxxxxx>
> > Acked-by: Eduard Zingerman <eddyz87@xxxxxxxxx>
> > Link: https://lore.kernel.org/bpf/20250729094611.2065713-1-fossdd@xxxxxxxxxx/
>
> Oops, the subject should've been v2. I forgot to pass -v2 to git
> send-email.

No. It was already applied.





[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux