linux-kernel - Re: [tip:x86/microcode 1/1] arch/x86/kernel/cpu/microcode/amd.c:714:6: warning: variable 'equiv_id' is used uninitialized whenever 'if' condition is false

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: <20240730014331.GB685493@thelio-3990X>
Date: Mon, 29 Jul 2024 18:43:31 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: kernel test robot <lkp@...el.com>, llvm@...ts.linux.dev,
	oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
	x86@...nel.org
Subject: Re: [tip:x86/microcode 1/1]
 arch/x86/kernel/cpu/microcode/amd.c:714:6: warning: variable 'equiv_id' is
 used uninitialized whenever 'if' condition is false

On Mon, Jul 29, 2024 at 06:50:36PM +0200, Borislav Petkov wrote:
> On Mon, Jul 29, 2024 at 08:30:08AM -0700, Nathan Chancellor wrote:
> > It's not behind W=1, this happens in a normal build:
> 
> "reproduce (this is a W=1 build):"
> 
> I guess that mail formulation is misleading.

Yeah, I can definitely see how that can be misleading. It might be nice
if the robot could do a regular and a W=1 build at the same time to
report which warnings show up at which levels. For the record/future,
-Wsometimes-uninitialized and -Wuninitialized from clang should always
appear in a normal build; if they don't, that's a bug.

> Ok, lemme fix that then.

Thanks a lot :)

Cheers,
Nathan