** Description changed: [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 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly + These can be picked from my branches here: + Bionic + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic + Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic + Disco: + https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco + + I do not believe these are necessary for Eoan, 5.1 should already + include them but it's worth verifying that as I started work on this + prior to Eoan's cycle. + [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu*
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
