[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190329162636.GA29901@8bytes.org>
Date: Fri, 29 Mar 2019 17:26:42 +0100
From: Joerg Roedel <joro@...tes.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.1-rc3
Hi Linus,
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v5.1-rc3
for you to fetch changes up to 8aafaaf2212192012f5bae305bb31cdf7681d777:
iommu/amd: Reserve exclusion range in iova-domain (2019-03-29 17:12:57 +0100)
----------------------------------------------------------------
IOMMU Fixes for Linux v5.1-rc3
Including:
- 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).
----------------------------------------------------------------
Joerg Roedel (2):
iommu: Don't print warning when IOMMU driver only supports unmanaged domains
iommu/amd: Reserve exclusion range in iova-domain
drivers/iommu/amd_iommu.c | 9 ++++++---
drivers/iommu/amd_iommu_init.c | 7 ++++---
drivers/iommu/amd_iommu_types.h | 2 ++
drivers/iommu/iommu.c | 8 +++++---
4 files changed, 17 insertions(+), 9 deletions(-)
Please pull.
Thanks,
Joerg
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists