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 v4.3-rc7
Date: Mon, 26 Oct 2015 17:19:59 +0900	[thread overview]
Message-ID: <20151026081958.GA7672@8bytes.org> (raw)

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

Hi Linus,

The following changes since commit 5adad9915472e180712030d730cdc476c6f8a60b:

  iommu/amd: Fix NULL pointer deref on device detach (2015-10-09 17:59:33 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.3-rc7

for you to fetch changes up to cbf3ccd09d683abf1cacd36e3640872ee912d99b:

  iommu/amd: Don't clear DTE flags when modifying it (2015-10-21 11:29:06 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v4.3-rc7

Two late fixes for the AMD IOMMU driver:

	* One adds an additional check to the io page-fault handler to
	  avoid a BUG_ON being hit in handle_mm_fault()

	* Second patch fixes a problem with devices writing to the
	  system management area and were blocked by the IOMMU because
	  the driver wrongly cleared out the DTE flags allowing that
	  access.

----------------------------------------------------------------
Jay Cornwall (1):
      iommu/amd: Fix BUG when faulting a PROT_NONE VMA

Joerg Roedel (1):
      iommu/amd: Don't clear DTE flags when modifying it

 drivers/iommu/amd_iommu.c       | 4 ++--
 drivers/iommu/amd_iommu_types.h | 1 +
 drivers/iommu/amd_iommu_v2.c    | 7 +++++++
 3 files changed, 10 insertions(+), 2 deletions(-)

Please pull.

Thanks,

	Joerg


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

                 reply	other threads:[~2015-10-26  8:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151026081958.GA7672@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).