*** This bug is a duplicate of bug 1959384 ***
https://bugs.launchpad.net/bugs/1959384
** This bug has been marked a duplicate of bug 1959384
CONFIG_IO_STRICT_DEVMEM could be enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package linux - 5.8.0-16.17
---
linux (5.8.0-16.17) groovy; urgency=medium
* groovy/linux: 5.8.0-16.17 -proposed tracker (LP: #1891233)
* Miscellaneous Ubuntu changes
- hio -- Update to use bio_{start,end}_io_acct with 5.8+
- Enable hio driver
This change was applied during the Focal development cycle but then
reverted pending performance testing results. That performance testing
work was never finished and I'm no longer working on this bug.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Triaged
** Changed in: linux
The problem is still there in Ubuntu 20.04/focal:
$ grep CONFIG_IO_STRICT_DEVMEM /boot/config-5.*
/boot/config-5.4.0-21-generic:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.4.0-21-lowlatency:# CONFIG_IO_STRICT_DEVMEM is not set
/boot/config-5.6.3-050603-generic:# CONFIG_IO_STRICT_DEVMEM is
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855338
Title:
CONFIG_IO_STRICT_DEVMEM should be enabled
To manage
** Description changed:
-
+ We should enable CONFIG_IO_STRICT_DEVMEM to restrict userspace access of
+ active io-memory ranges.
+
+ This could impact kernel debugability. In that case, you may reboot with
+ iomem=relaxed on the kernel commandline to override this setting.
+
+
+ This config
