linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [git pull] IOMMU Fixes for Linux v5.1-rc3
Date: Fri, 29 Mar 2019 17:26:42 +0100	[thread overview]
Message-ID: <20190329162636.GA29901@8bytes.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-03-29 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 16:26 Joerg Roedel [this message]
2019-03-29 22:55 ` [git pull] IOMMU Fixes for Linux v5.1-rc3 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190329162636.GA29901@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).