public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [git pull] IOMMU Fixes for Linux v6.11-rc5
Date: Fri, 30 Aug 2024 14:48:49 +0200	[thread overview]
Message-ID: <ZtG_sa5UUrAoYkKd@8bytes.org> (raw)

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

Hi Linus,

The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:

  Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git tags/iommu-fixes-v6.11-rc5

for you to fetch changes up to 51eeef9a482bcb00f6f75eda4de9bd013092b76f:

  MAINTAINERS: Add Jean-Philippe as SMMUv3 SVA reviewer (2024-08-26 09:17:36 +0200)

----------------------------------------------------------------
IOMMU Fixes for Linux v6.11-rc5

Including:

	- Fix a device-stall problem in bad io-page-fault setups (faults
	  received from devices with no supporting domain attached).

	- Context flush fix for Intel VT-d.

	- Do not allow non-read+non-write mapping through iommufd as most
	  implementations can not handle that.

	- Fix a possible infinite-loop issue in map_pages() path.

	- Add Jean-Philippe as reviewer for SMMUv3 SVA support

----------------------------------------------------------------
Jason Gunthorpe (2):
      iommufd: Do not allow creating areas without READ or WRITE
      iommu: Do not return 0 from map_pages if it doesn't do anything

Lu Baolu (1):
      iommu/vt-d: Fix incorrect domain ID in context flush helper

Pranjal Shrivastava (1):
      iommu: Handle iommu faults for a bad iopf setup

Will Deacon (1):
      MAINTAINERS: Add Jean-Philippe as SMMUv3 SVA reviewer

 MAINTAINERS                                 |   4 +
 drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c |   2 +-
 drivers/iommu/intel/iommu.c                 |   8 +-
 drivers/iommu/intel/iommu.h                 |   2 +-
 drivers/iommu/intel/pasid.c                 |   7 +-
 drivers/iommu/io-pgfault.c                  | 121 +++++++++++++++++++---------
 drivers/iommu/io-pgtable-arm-v7s.c          |   3 +-
 drivers/iommu/io-pgtable-arm.c              |   3 +-
 drivers/iommu/io-pgtable-dart.c             |   3 +-
 drivers/iommu/iommufd/ioas.c                |   8 ++
 include/linux/iommu.h                       |   5 +-
 tools/testing/selftests/iommu/iommufd.c     |   6 +-
 12 files changed, 116 insertions(+), 56 deletions(-)

Please pull.

Thanks,

	Joerg

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

             reply	other threads:[~2024-08-30 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 12:48 Joerg Roedel [this message]
2024-08-30 18:37 ` [git pull] IOMMU Fixes for Linux v6.11-rc5 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=ZtG_sa5UUrAoYkKd@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.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