related branch
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco/+ref/amd-iommu-cherrypick
** Also affects: linux (Ubuntu Disco)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
** Changed in: linux (Ubuntu Cosmic)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Jeff Lane (bladernr)
--
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/1823037
Title:
amd_iommu possible data corruption
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
New
Status in linux source package in Cosmic:
New
Status in linux source package in Disco:
In Progress
Bug description:
[Impact]
If a device has an exclusion range specified in the IVRS table, this region
needs to be reserved in the iova-domain of that device. This hasn't happened
until now and can cause data corruption on data transfered with these devices.
Treat exclusion ranges as reserved regions in the iommu-core to fix the
problem.
This is a clean cherry pick from mainline of
8aafaaf2212192012f5bae305bb31cdf7681d777
[Test Case]
[Fixes]
Cherry pick the following from Mainline
fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range
in iova-domain
[Regression Risk]
Only affects the amd_iommu driver:
drivers/iommu/amd_iommu*
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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
