diff options
| author | Joerg Roedel <jroedel@suse.de> | 2019-03-28 11:44:59 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-05-04 09:20:22 +0200 |
| commit | 71f3397a1c311c7aad7d141871c5b3404d18b6d0 (patch) | |
| tree | 1326a9addb8cae8e4c395ca4e5ad993d8b404c08 /kernel/ptrace.c | |
| parent | 75a5e3e6340cc07c1f87dcd7b82596a308c7e9fb (diff) | |
| download | linux-stable-71f3397a1c311c7aad7d141871c5b3404d18b6d0.tar.gz linux-stable-71f3397a1c311c7aad7d141871c5b3404d18b6d0.tar.bz2 linux-stable-71f3397a1c311c7aad7d141871c5b3404d18b6d0.zip | |
iommu/amd: Reserve exclusion range in iova-domain
[ Upstream commit 8aafaaf2212192012f5bae305bb31cdf7681d777 ]
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.
Fixes: be2a022c0dd0 ('x86, AMD IOMMU: add functions to parse IOMMU memory mapping requirements for devices')
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: Gary R Hook <gary.hook@amd.com>
Signed-off-by: Sasha Levin (Microsoft) <sashal@kernel.org>
Diffstat (limited to 'kernel/ptrace.c')
0 files changed, 0 insertions, 0 deletions