linux-kernel - Re: [tip:x86/urgent 1/1] arch/x86/coco/sev/core.c:2170:30: warning: variable 'dummy' set but not used

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] [day] [month] [year] [list]

Message-ID: <20250702210254.GA3996668@ax162>
Date: Wed, 2 Jul 2025 14:02:54 -0700
From: Nathan Chancellor <nathan@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: kernel test robot <lkp@...el.com>, Nikunj A Dadhania <nikunj@....com>,
	llvm@...ts.linux.dev, oe-kbuild-all@...ts.linux.dev,
	linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [tip:x86/urgent 1/1] arch/x86/coco/sev/core.c:2170:30: warning:
 variable 'dummy' set but not used

On Tue, Jul 01, 2025 at 05:29:53PM +0200, Borislav Petkov wrote:
> On Tue, Jul 01, 2025 at 08:06:44AM -0700, Nathan Chancellor wrote:
> > Citation needed. This reproduces with Clang 15 (earliest supported on
> > x86 now), Clang 19, and GCC 15 for me. Were you missing W=1?
> 
> Nope.
> 
> $ git checkout -b test 4a35d2b5254af89595fd90dae9ee0c8f990a148d
> Switched to a new branch 'test'
> $ make CC=clang-19 HOSTCC=clang-19 W=1 arch/x86/coco/sev/core.o
> ...
>   LINK    /mnt/kernel/kernel/linux/tools/objtool/objtool
>   CC      arch/x86/coco/sev/core.o
> $ clang-19 --version
> Debian clang version 19.1.7 (1+b1)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> InstalledDir: /usr/lib/llvm-19/bin

Spooky, same SHA, build command, and configuration from this thread with

  Debian clang version 19.1.7 (3+b1)
  Target: x86_64-pc-linux-gnu
  Thread model: posix
  InstalledDir: /usr/lib/llvm-19/bin

from unstable Debian (since it is what I base on for my Debian
development container) shows it for me... Can't imagine the two Debian
patch levels would have caused anything here but it is probably not
worth thinking too much more about since it is already resolved.

Cheers,
Nathan