This bug was fixed in the package linux - 6.8.0-20.20
---------------
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CLEAR_CPU_BUF is set
- Documentation/hw-vuln: Add documentation for RFDS
- x86/rfds: Mitigate Register File Data Sampling (RFDS)
- KVM/x86: Export RFDS_NO and RFDS_CLEAR to guests
- Linux 6.8.1
* Autopkgtest failures on amd64 (LP: #2048768)
- [Packaging] update to clang-18
* Miscellaneous Ubuntu changes
- SAUCE: apparmor4.0.0: LSM stacking v39: fix build error with
CONFIG_SECURITY=n
- [Config] amd64: MITIGATION_RFDS=y
-- Paolo Pisati <paolo.pis...@canonical.com> Mon, 18 Mar 2024 11:08:14
+0100
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
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/1951440
Title:
Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Invalid
Status in linux source package in Noble:
Fix Released
Bug description:
Starting with the following commit, upstream kernel is enabling Intel
IOMMU related options by default:
792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
default")
We should follow upstream direction enabling
CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON.
A downside is that this change may introduce boot regressions on old
systems (especially those with buggy firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440/+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
