From: Nikolay Borisov <nik.borisov@suse.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Dave Hansen <dave.hansen@intel.com>
Cc: "Chang S. Bae" <chang.seok.bae@intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org, tglx@kernel.org,
Ingo Molnar <mingo@redhat.com>,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com
Subject: Re: [PATCH] x86/microcode/intel: Panic on partial microcode update
Date: Mon, 27 Jul 2026 15:35:40 +0300 [thread overview]
Message-ID: <85130986-aba9-43c5-8cee-aac3b8ce2ae4@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2607210121460.64835@angie.orcam.me.uk>
On 7/24/26 01:42, Maciej W. Rozycki wrote:
> We aim not to set a policy either, but at this point we have become aware
> the CPU is in a bad state, so I think at the very least there needs to be
> a way for the site manager to configure handling according to their needs,
> and I think it should be killing the system by default.
For people who care that much about this, they likely are running huge
fleets and already have daemons/agents(sic) which are monitoring dmesg
and are taking actions accordingly. So that use case is not lost.
next prev parent reply other threads:[~2026-07-27 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 19:13 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 [this message]
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
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=85130986-aba9-43c5-8cee-aac3b8ce2ae4@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--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®