linux-kernel - Re: [PATCH v2 1/1] x86/reboot: KVM: Guard nmi_shootdown_cpus_on

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: <f670905f-f14b-4482-83ee-568234647f46@intel.com>
Date: Tue, 8 Apr 2025 07:17:51 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Sean Christopherson <seanjc@...gle.com>
Cc: linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
 x86@...nel.org, "H. Peter Anvin" <hpa@...or.com>,
 Nathan Chancellor <nathan@...nel.org>,
 Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling
 <morbo@...gle.com>, Justin Stitt <justinstitt@...gle.com>
Subject: Re: [PATCH v2 1/1] x86/reboot: KVM: Guard
 nmi_shootdown_cpus_on_restart() with ifdeffery

On 4/8/25 05:19, Andy Shevchenko wrote:
> Any news here? Build error is still reproducible.

In the end, adding the #ifdefs leads to worse code, less maintainable
code. I'll take the occasional actual unused static inline in a .c file
over a mess of #ifdefs to make the compiler happy.

I really think that warning needs to go away in some way, shape or form.
Either get rid of it entirely, or kick it out of -Wall somehow. It's a
super pedantic warning that leads to worse code most of the time.