mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikolay Borisov <nik.borisov@suse.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, hpa@zytor.com
Subject: Re: [PATCH v2] x86/microcode/intel: Taint kernel on partial update
Date: Mon, 27 Jul 2026 14:27:56 +0300	[thread overview]
Message-ID: <8fc96401-5e1f-41a1-ab14-3a27c4f4b813@suse.com> (raw)
In-Reply-To: <20260708211803.402467-1-chang.seok.bae@intel.com>



On 7/9/26 00:18, Chang S. Bae wrote:
> A modern individual microcode update contains firmware for many pieces of
> silicon inside the CPU. Sometimes, a single update operation successfully
> updates some components and not others leaving a partially-applied
> update.
> 
> This may leave the system in an undefined and unreliable state. Fatal
> failures are expected to be handled by the CPU itself, by raising #MC for
> example. If the CPU instead reports a partial update, warn and taint the
> kernel at least.
> 
> A partial update may still update the revision. Continue checking the
> revision rather than an immediate error return so the update result
> remains consistent with the revision changes.
> 
> Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
> ---
> V1 -> V2: Do not raise panic, inline cpuid check and massage the changelog (Dave)


Reviewed-by: Nikolay Borisov <nik.borisov@suse.com>


<rant>
What a long-winded way to check whether MCU_ENUM is present... I 
understand it's outside of the purview of software but couldn't this 
been put into some customs CPUID leaf ... sigh
</rant>

      reply	other threads:[~2026-07-27 11:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 19:13 [PATCH] x86/microcode/intel: Panic on partial microcode update Chang S. Bae
2026-06-30 21:38 ` Dave Hansen
2026-06-30 21:47   ` Dave Hansen
2026-06-30 23:21     ` Borislav Petkov
2026-07-01 19:02     ` Chang S. Bae
2026-07-18 22:54     ` Maciej W. Rozycki
2026-07-19 15:52       ` Dave Hansen
2026-07-23 22:42         ` Maciej W. Rozycki
2026-07-27 12:35           ` Nikolay Borisov
2026-07-28 21:53             ` Maciej W. Rozycki
2026-07-27 20:36         ` Chang S. Bae
2026-07-27 21:59           ` Sohil Mehta
2026-07-28  2:58             ` Chang S. Bae
2026-07-28 14:12               ` Dave Hansen
2026-07-28 18:56                 ` David Laight
2026-07-28 20:48                   ` Dave Hansen
2026-07-28 21:47                     ` Maciej W. Rozycki
2026-07-28 21:53                       ` Dave Hansen
2026-07-28 22:09                     ` David Laight
2026-07-08 21:18 ` [PATCH v2] x86/microcode/intel: Taint kernel on partial update Chang S. Bae
2026-07-27 11:27   ` Nikolay Borisov [this message]

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=8fc96401-5e1f-41a1-ab14-3a27c4f4b813@suse.com \
    --to=nik.borisov@suse.com \
    --cc=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@kernel.org \
    --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®