Re: [PATCH] x86/microcode/intel: Panic on partial microcode update

[Borislav Petkov]

On Tue, Jun 30, 2026 at 02:47:46PM -0700, Dave Hansen wrote:
> Thinking about this a bit more: I don't think we should panic. It's
> perfectly fine to spew a nice scary warning. But we really should
> continue unless we really *know* that something has gone so horribly
> wrong that it's dangerous to continue.
> 
> Think about things like folks who are ssh'd in. Say they have a bad,
> partial ucode update. With this approach, they get a dead ssh session.
> 
> If you WARN() and keep going, they at least have a chance of seeing the
> spew and getting it off the system.
> 
> I mean, the ucode update guys themselves could definitely have reset the
> system if it needed to. They also know when it is dangerous to keep the
> CPU running. They obviously don't think that this partial update thing
> is *THAT* dangerous or they wouldn't have even let the CPU keep
> churning. Right?

You want to taint because panic_on_warn will kill the system.

But lemme look at v2 first in detail, once it appears...

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette