diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2019-03-29 15:37:10 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-03-29 15:37:10 -0700 |
| commit | c0b7f2a5fb957f2d5429b603b1a131ed7c8b4a30 (patch) | |
| tree | 987dbfc402f6f346ddd81fe319c951b6e79fa099 /.cocciconfig | |
| parent | eed4897dfe8a9743c998ebb57f86e146864ffa94 (diff) | |
| parent | 8aafaaf2212192012f5bae305bb31cdf7681d777 (diff) | |
| download | linux-c0b7f2a5fb957f2d5429b603b1a131ed7c8b4a30.tar.bz2 | |
Merge tag 'iommu-fixes-v5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu
Pull IOMMU fixes from Joerg Roedel:
- Fix a bug in the AMD IOMMU driver not handling exclusion ranges
correctly. In fact the driver did not reserve these ranges for IOVA
allocations, so that dma-handles could be allocated in an exclusion
range, leading to data corruption. Exclusion ranges have not been
used by any firmware up to now, so this issue remained undiscovered
for quite some time.
- Fix wrong warning messages that the IOMMU core code prints when it
tries to allocate the default domain for an iommu group and the
driver does not support any of the default domain types (like Intel
VT-d).
* tag 'iommu-fixes-v5.1-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
iommu/amd: Reserve exclusion range in iova-domain
iommu: Don't print warning when IOMMU driver only supports unmanaged domains
Diffstat (limited to '.cocciconfig')
0 files changed, 0 insertions, 0 deletions