netdev - Re: [net-next,v2] net: ravb: Fix -Wmaybe-uninitialized warning

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: <20250915183722.50e83484@kernel.org>
Date: Mon, 15 Sep 2025 18:37:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Niklas Söderlund
 <niklas.soderlund+renesas@...natech.se>
Cc: Paul Barker <paul@...rker.dev>, Andrew Lunn <andrew+netdev@...n.ch>,
 "David S. Miller" <davem@...emloft.net>, Eric Dumazet
 <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
 netdev@...r.kernel.org, linux-renesas-soc@...r.kernel.org, Przemek Kitszel
 <przemyslaw.kitszel@...el.com>
Subject: Re: [net-next,v2] net: ravb: Fix -Wmaybe-uninitialized warning

On Sat, 13 Sep 2025 15:32:29 +0200 Niklas Söderlund wrote:
> Fix a -Wmaybe-uninitialized warning by initializing the variable to
> NULL. The warning is bogus and should not happen, but fixing it allows
> running the check on the driver to catch potential future problems.
> 
>   $ make CFLAGS_ravb_main.o=-Wmaybe-uninitialized

FWIW this is why kernel only enables this warning at W=2 for gcc.
Clang appears to suck much less in detecting uninitialized variables.
Testing with both compilers at W=1 is usually better for one's sanity
than trying to fix W=2 warnings.