linux-kernel - Re: [PATCH] x86/its: Warn when microcode is old

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: <29314698-8c7d-4088-b391-6c33c21acc84@intel.com>
Date: Thu, 12 Jun 2025 06:31:39 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
 Sohil Mehta <sohil.mehta@...el.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
 Borislav Petkov <bp@...en8.de>, Josh Poimboeuf <jpoimboe@...nel.org>,
 Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH] x86/its: Warn when microcode is old

On 6/12/25 06:19, Pawan Gupta wrote:
> On a second thought, cpu_set_bug_bits() already issues a warning, and even
> taints the kernel when old microcode is detected. So warning here seems
> redundant, and also misleading as you said. I am okay dropping this patch.

Yep, that was the whole point of X86_BUG_OLD_MICROCODE. It's one, big,
bad, scary warning so that we don't have to do it for all the individual
little bad things that happen when you have old microcode.