linux-kernel - Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum ucode revisions

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: <4d5a17d5-f26a-4682-ab7b-5a3b05b5af3a@intel.com>
Date: Fri, 22 Aug 2025 11:31:40 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Borislav Petkov <bp@...en8.de>, Sohil Mehta <sohil.mehta@...el.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
 Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
 "H . Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
 Josh Poimboeuf <jpoimboe@...nel.org>,
 Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
 Nikolay Borisov <nik.borisov@...e.com>,
 Andrew Cooper <andrew.cooper3@...rix.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum
 ucode revisions

On 8/22/25 11:24, Borislav Petkov wrote:
> Update to the header needs to happen in very controlled manner, when you have
> released tested microcode and have decided to deprecate old microcode.

Right. It'll happen in response to a public microcode release.

> So, actually, this script should NOT be in the kernel but in some repo
> internal in Intel.

We could definitely put it there. But it's generating a 100%
Linux-specific header that nobody else can use. So it's really a purely
Linux thing. Not really a great fit for what is otherwise just a
microcode repository.

I honestly don't care that much if it's in the kernel tree or not. The
best part for me of having it in the kernel is that it makes it easier
for _anybody_ to just go make a patch to update the header when I'm too
lazy to do it.

I'll probably just go stick it in some other kernel.org repo if folks
don't want it upstream.