From: Jason Gunthorpe <jgg@nvidia.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>
Subject: [GIT PULL] Please pull IOMMUFD subsystem changes
Date: Thu, 22 Oct 2026 13:51:51 -0300 [thread overview]
Message-ID: <20261022165151.GA3692244@nvidia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3366 bytes --]
Hi Linus,
Small set of iommufd updates this cycle, pretty much all bug fixes
Thanks,
Jason
The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:
Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git tags/for-linus-iommufd
for you to fetch changes up to 04bcf84613346b973a8cc0c59238b6b5bc902688:
iommupt: Do not allow PTEs to be split when dirty logging (2026-10-15 13:56:22 -0300)
----------------------------------------------------------------
iommufd v7.4 merge window pull request
Several bug fixes, probably found by AI based on the emails:
- Several edge cases in the self test
- Reject malformed invalidation commands in case the VMM let them through
- Rework how the invalidation interface works to the drivers to be more
robust and fix several Sashiko issues
- Correct several error unwind paths
- UAF during eventq file release
- Reject more malformed usage of the dirty tracking by the VMM
----------------------------------------------------------------
Andrea Parri (3):
iommufd: Keep dmabuf PFNs MMIO when filling another domain
iommufd: Reject a zero-length dirty bitmap request
iommufd/iova_bitmap: Ensure that iova_bitmap_set() handles the full IOVA
Donggeun Yoo (1):
iommufd: Keep reserved IOVA ranges when a replace within one IOAS fails
Eva Kurchatova (1):
iommufd/selftest: Skip when the mock device is not there
Jason Gunthorpe (1):
iommupt: Do not allow PTEs to be split when dirty logging
Karl Mehltretter (1):
iommufd: Fix iommufd_hw_capabilities reference in kernel-doc
Nicolin Chen (5):
iommu/arm-smmu-v3-iommufd: Reject unsupported bits in invalidation commands
iommufd: Iterate the cache invalidation array in the core
iommufd/selftest: Convert cache invalidation mocks to the core array loop
iommu/arm-smmu-v3-iommufd: Convert cache invalidation to the core array loop
iommu/vt-d: Convert nested cache invalidation to the core array loop
Nirmoy Das (1):
iommufd: Fix event queue release use-after-free
Qinyun Tan (1):
iommufd/selftest: Return dmabuf fd from IOMMU_TEST_OP_DMABUF_GET again
Samarth Narang (1):
iommufd/iova_bitmap: Fail GET_DIRTY_BITMAP when a bitmap page cannot be pinned
.../iommu/arm/arm-smmu-v3/arm-smmu-v3-iommufd.c | 197 ++++++++++++++++-----
drivers/iommu/generic_pt/iommu_pt.h | 30 +---
drivers/iommu/intel/nested.c | 54 +++---
drivers/iommu/iommufd/device.c | 8 +-
drivers/iommu/iommufd/eventq.c | 4 +-
drivers/iommu/iommufd/hw_pagetable.c | 25 +--
drivers/iommu/iommufd/io_pagetable.c | 5 +-
drivers/iommu/iommufd/iova_bitmap.c | 26 ++-
drivers/iommu/iommufd/pages.c | 13 +-
drivers/iommu/iommufd/selftest.c | 153 ++++++++--------
include/linux/iommu.h | 6 +-
include/linux/iommufd.h | 2 +
include/uapi/linux/iommufd.h | 12 +-
tools/testing/selftests/iommu/iommufd.c | 24 ++-
tools/testing/selftests/iommu/iommufd_fail_nth.c | 14 +-
15 files changed, 375 insertions(+), 198 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-10-22 16:51 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 16:51 Jason Gunthorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-18 20:36 Jason Gunthorpe
2026-08-19 19:54 ` pr-tracker-bot
2026-07-30 21:34 Jason Gunthorpe
2026-07-30 22:15 ` pr-tracker-bot
2026-06-17 17:30 Jason Gunthorpe
2026-06-17 19:40 ` pr-tracker-bot
2026-04-16 17:33 Jason Gunthorpe
2026-04-17 4:27 ` pr-tracker-bot
2026-01-30 23:41 Jason Gunthorpe
2026-01-31 1:20 ` pr-tracker-bot
2025-12-18 18:52 Jason Gunthorpe
2025-12-18 20:39 ` pr-tracker-bot
2025-12-02 17:50 Jason Gunthorpe
2025-12-05 3:01 ` pr-tracker-bot
2025-11-25 15:09 Jason Gunthorpe
2025-11-25 16:38 ` pr-tracker-bot
2025-11-07 18:51 Jason Gunthorpe
2025-11-07 21:21 ` pr-tracker-bot
2025-10-02 14:29 Jason Gunthorpe
2025-10-04 1:40 ` pr-tracker-bot
2025-09-22 14:33 Jason Gunthorpe
2025-09-22 18:27 ` pr-tracker-bot
2025-08-22 14:21 Jason Gunthorpe
2025-08-22 21:28 ` pr-tracker-bot
2025-07-30 18:47 Jason Gunthorpe
2025-07-31 20:01 ` pr-tracker-bot
2025-07-02 14:14 Jason Gunthorpe
2025-07-02 17:06 ` pr-tracker-bot
2025-03-31 16:12 Jason Gunthorpe
2025-04-02 1:50 ` pr-tracker-bot
2025-01-23 16:59 Jason Gunthorpe
2025-01-24 21:45 ` pr-tracker-bot
2024-12-05 18:44 Jason Gunthorpe
2024-12-05 23:08 ` pr-tracker-bot
2024-11-20 14:53 Jason Gunthorpe
2024-11-21 21:20 ` pr-tracker-bot
2024-09-23 17:45 Jason Gunthorpe
2024-09-24 19:36 ` pr-tracker-bot
2024-08-20 22:48 Jason Gunthorpe
2024-08-20 23:52 ` pr-tracker-bot
2024-07-17 18:46 Jason Gunthorpe
2024-07-19 18:09 ` pr-tracker-bot
2024-04-19 17:29 Jason Gunthorpe
2024-04-19 21:07 ` pr-tracker-bot
2024-03-02 0:08 Jason Gunthorpe
2024-03-02 1:31 ` pr-tracker-bot
2024-02-22 13:23 Jason Gunthorpe
2024-02-22 20:03 ` pr-tracker-bot
2024-01-12 17:49 Jason Gunthorpe
2024-01-18 23:35 ` pr-tracker-bot
2023-12-04 19:35 Jason Gunthorpe
2023-12-04 21:59 ` pr-tracker-bot
2023-10-31 13:14 Jason Gunthorpe
2023-11-02 2:51 ` pr-tracker-bot
2023-08-30 23:40 Jason Gunthorpe
2023-08-31 3:50 ` pr-tracker-bot
2023-08-31 3:59 ` Linus Torvalds
2023-08-31 16:43 ` Jason Gunthorpe
2023-07-28 13:48 Jason Gunthorpe
2023-07-28 18:39 ` pr-tracker-bot
2023-06-28 14:04 Jason Gunthorpe
2023-06-30 4:16 ` pr-tracker-bot
2023-04-25 14:46 Jason Gunthorpe
2023-04-27 17:15 ` pr-tracker-bot
2023-04-06 13:34 Jason Gunthorpe
2023-04-06 18:46 ` pr-tracker-bot
2023-02-21 15:39 Jason Gunthorpe
2023-02-24 22:50 ` Linus Torvalds
2023-02-25 0:02 ` Jason Gunthorpe
2023-02-25 0:50 ` Linus Torvalds
2023-02-24 23:27 ` pr-tracker-bot
2022-12-12 18:30 Jason Gunthorpe
2022-12-14 18:04 ` 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=20261022165151.GA3692244@nvidia.com \
--to=jgg@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.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®