linux-kernel - Re: [PATCH] [v4] x86/cpu: Help users notice when running old Intel microcode

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: <f642ec94-4917-4124-9ec5-3885d92492e3@intel.com>
Date: Thu, 6 Feb 2025 21:04:49 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Alex Murray <alex.murray@...onical.com>,
 Dave Hansen <dave.hansen@...ux.intel.com>, linux-kernel@...r.kernel.org
Cc: x86@...nel.org, tglx@...utronix.de, bp@...en8.de,
 andrew.cooper3@...rix.com
Subject: Re: [PATCH] [v4] x86/cpu: Help users notice when running old Intel
 microcode

On 2/6/25 17:47, Alex Murray wrote:
>> Also note that the "intel-ucode-defs.h" file is simple, ugly and
>> has lots of magic numbers. That's on purpose and should allow a
>> single file to be shared across lots of stable kernel regardless of if
>> they have the new "VFM" infrastructure or not. It was generated with
>> a dumb script.
>>
> Should this script be included as part of this patch so that it is easy
> for others to update intel-ucode-defs.h if needed in the future?

I was planning on throwing it in the tree _somewhere_ at some point.
Here's a copy for now in case anyone wants to take a look. I assume
folks would rather it live in the kernel tree in scripts/ rather than
somewhere else.

The other thing I was toying with was trying to get Intel to run it as a
part of the microcode release process. That way, we could just copy the
file from the microcode repo and wouldn't have to run a script at all.

I'll post it as part of a real patch at some point.
View attachment "ucode-versions.py" of type "text/x-python" (1755 bytes)