Re: x86, microcode: BUG: microcode update that changes x86_capability
From: Borislav Petkov
Date: Thu Sep 25 2014 - 10:57:07 EST
On Thu, Sep 25, 2014 at 11:40:25AM -0300, Henrique de Moraes Holschuh wrote:
> At this point, what alternatives are left?
Here's what we could do:
* Install microcode to /lib/firmware/...
* Refuse to update the microcode and tell the user that she needs to reboot.
* Reboot and load the microcode
For that to work though, we'd need to detect the that we're freshly
booting and only then load the microcode (if we're coming in later,
we should refuse because something linking to libpthread might've run
Now, we need to think about how to detect that reliably, if at all
The other thing we could do is backport early ucode loading...
Hmm, I'm not crazy about both possibilities though, TBH.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/