From: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, sohil.mehta@intel.com,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@redhat.com>, Jon Kohler <jon@nutanix.com>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
Tony Luck <tony.luck@intel.com>,
x86@kernel.org
Subject: Re: [PATCH 0/6] x86/cpu: Take Intel platform into account for old microcode checks
Date: Fri, 23 Jan 2026 09:26:28 +0000 [thread overview]
Message-ID: <aXM95mvmqZWMhpUa@wieczorr-mobl1.localdomain> (raw)
Tested the patchset by fabricating the scenario described below. No issues were
observed and the 'Running old microcode' warning has dissapeared after applying
the patches.
Tested-by: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Kind regards
Maciej Wieczór-Retman
(resending this email because I noticed the in-reply-to got lost for some
reason)
On 2026-01-19 at 11:50:47 -0800, Dave Hansen wrote:
>There was a report[1] that CPUs running updated microcode were being
>reported as running old microcode. The reason is that the old
>microcode list neglects to take the platform ID into account.
>
>The platform ID is an Intel-only construct that allows CPUs that
>otherwise have the same model/family/stepping to take different
>microcode revisions. The microcode loader itself already checks this.
>Only the recent "old_microcode" checker failed here.
>
>Treat the platform ID as a peer of model/family/stepping. Store it
>in 'struct cpuinfo_x86', enable matching on it with with 'struct
>x86_cpu_id', and flesh out the 'old_microcode' list with it.
>
>This fixes the report of an inaccurate, false positive in the
>'old_microcode' vulnerability file.
>
>1. https://lore.kernel.org/all/38660F8F-499E-48CD-B58B-4822228A5941@nutanix.com/
next reply other threads:[~2026-01-23 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 9:26 Maciej Wieczor-Retman [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-20 21:31 Maciej Wieczor-Retman
2026-01-19 19:50 Dave Hansen
2026-01-20 18:18 ` Dave Hansen
2026-01-22 13:56 ` Ricardo Neri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aXM95mvmqZWMhpUa@wieczorr-mobl1.localdomain \
--to=m.wieczorretman@pm.me \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jon@nutanix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®