On Sat, 8 Oct 2022 at 07:00, Steve Langasek <email address hidden>
wrote:
> > While we could assume that users have up-to-date microcode on a running
> > system, this issue could manifest when trying to install Ubuntu on a
> fresh
> > computer *before* the user had a chance to update the microcode.
>
> This doesn't block acceptance of the upload, but microcode updates are
> supposed to be applied to the CPU from early boot by the kernel via the
> initramfs, including in install images; so why is this a concern in
> practice?
>
I think the more realistic scenario is a 22.10 container on an OS that does
not mandate microcode updates. Also I don't know if all processors that are
affected by this will get the relevant instructions enabled by an
up-to-date microcode (I haven't even looked into this at all though).
On Sat, 8 Oct 2022 at 07:00, Steve Langasek <email address hidden>
wrote:
> > While we could assume that users have up-to-date microcode on a running
> > system, this issue could manifest when trying to install Ubuntu on a
> fresh
> > computer *before* the user had a chance to update the microcode.
>
> This doesn't block acceptance of the upload, but microcode updates are
> supposed to be applied to the CPU from early boot by the kernel via the
> initramfs, including in install images; so why is this a concern in
> practice?
>
I think the more realistic scenario is a 22.10 container on an OS that does
not mandate microcode updates. Also I don't know if all processors that are
affected by this will get the relevant instructions enabled by an
up-to-date microcode (I haven't even looked into this at all though).