netdev - Re: [PATCH net-next] tools: ynl: avoid "use of uninitialized variable" false positive in generated code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250915144052.6cbbe120@kernel.org>
Date: Mon, 15 Sep 2025 14:40:52 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: netdev@...r.kernel.org, Donald Hunter <donald.hunter@...il.com>, "David
 S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
 Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>
Subject: Re: [PATCH net-next] tools: ynl: avoid "use of uninitialized
 variable" false positive in generated code

On Mon, 15 Sep 2025 17:44:14 +0300 Vladimir Oltean wrote:
> It is a pity that we have to do this, but I see no other way than to
> suppress the false positive by appeasing the compiler and initializing
> the "*attr_{aspec.c_name}" variable with a bogus value (NULL). This will
> never be used - at runtime it will always be overwritten when
> "n_{struct[anest].c_name}" is non-zero.

Yeah, I'm hitting this on CentOS, too :(

Reviewed-by: Jakub Kicinski <kuba@...nel.org>