mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: joro@8bytes.org, linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] IOMMU Fixes for Linux v7.2-rc5
Date: Fri, 24 Jul 2026 17:25:44 +0100	[thread overview]
Message-ID: <amOSCGEa5N4lEUFM@willie-the-truck> (raw)

Hi Linus,

Joerg's away at the moment so I've been looking after the IOMMU tree in
his absence. In the process of doing that, I've hoovered up a handful
of fixes for the AMD and Intel drivers which address a combination of
the usual out-of-bounds/locking/leak bugs as well as some logical issues
around SVA and command completion.

Summary in the tag; please pull.

Cheers,

Will

--->8

The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:

  Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iommu/linux.git tags/iommu-fixes-v7.2-rc5

for you to fetch changes up to 754f8efe45f87e3a9c6871b645b2f9d46d1b407b:

  iommu/intel: Fix out-of-bounds memset in dmar_latency_disable() (2026-07-21 11:34:51 +0000)

----------------------------------------------------------------
IOMMU Fixes for Linux v7.2-rc5

- AMD:
  * Fix lockdep splat from nested domain allocation

  * Fix nested domain leak

  * Fix broken synchronisation of command completion

  * Fix OOB write in "ivrs_acpihid" command-line parsing

- VT-d:
  * Prevent SVA for IOMMUs with non-coherent page-table walker

  * Fix OOB write in PMU driver.

----------------------------------------------------------------
Guanghui Feng (1):
      iommu/amd: Wait for completion instead of returning early in iommu_completion_wait()

Li RongQing (1):
      iommu/intel: Fix out-of-bounds memset in dmar_latency_disable()

Lu Baolu (1):
      iommu/vt-d: Disallow SVA if page walk is not coherent

Pengpeng Hou (1):
      iommu/amd: Bound the early ACPI HID map

Tycho Andersen (AMD) (2):
      iommu/amd: Fix IRQ unsafe locking in gdom allocation
      iommu/amd: Fix nested domain leak

 drivers/iommu/amd/init.c   |  6 ++++++
 drivers/iommu/amd/iommu.c  | 22 ++++++++++++++++------
 drivers/iommu/amd/nested.c | 34 +++++++++++++++++++---------------
 drivers/iommu/intel/perf.c |  2 +-
 drivers/iommu/intel/svm.c  |  2 +-
 5 files changed, 43 insertions(+), 23 deletions(-)

             reply	other threads:[~2026-07-24 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 16:25 Will Deacon [this message]
2026-07-24 19:22 ` 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=amOSCGEa5N4lEUFM@willie-the-truck \
    --to=will@kernel.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.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

all inboxes | Powered by JetHome®