The verification of the Stable Release Update for qemu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790457 Title: kernel: improve spectre mitigation Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in qemu source package in Bionic: Fix Released Bug description: [Impact] * eToken Facility will help to mitigate spectre. With it in place use of expolines can be ommitted. Kernel https://github.com/torvalds/linux/commit/aeaf7002a76c8da60c0f503badcbddc07650678c KVM to pass it to guests: https://patchwork.kernel.org/patch/10532197/ * Backport the changes to Qemu/Kernel so that the impact of the spectre fixes can be minimized. [Test Case] * First of all you need HW with the facility available. For HW without nothing should change at all, well maybe a message that it wasn't detected when the new kernel boots. * When running on HW with the Facility and a fixed kernel then the facility should be reported as being available. * With a fixed Kernel AND Qemu this facility should be passed to the guest so that it can benefit from the improvements as well. * Due to a lack of such HW IBM volunteered to do the verification on this bug. [Regression Potential] * Detection and passing of a Facility is nothing new, s390x has plenty of them and this is in some sense "just one more" so regressions should be minimal. The one thing we thought about was how an enabled Kernel/qemu would behave on systems that do not have the facility, but in all tests that was correctly detected and continues to use expoline. [Other Info] * n/a --- Description will follow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790457/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp