All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 17 Jun 2026 14:30:54 -0300	[thread overview]
Message-ID: <20260617173054.GA235044@nvidia.com> (raw)

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

Hi Linus,

A bunch of fixes for AI found bugs.

Thanks,
Jason

The following changes since commit 7fd2df204f342fc17d1a0bfcd474b24232fb0f32:

  Linux 7.1-rc2 (2026-05-03 14:21:25 -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 e28bee5b445178390d63f7a93a5a219063c6434e:

  iommu: Avoid copying the user array twice in the full-array copy helper (2026-06-12 10:44:44 -0300)

----------------------------------------------------------------
iommufd v7.2 merge window pull request

All various fixes:

- Typo breaking the veventq uAPI for 32 bit userspace

- Several Sashiko found errors in the veventq and fault fd paths

- Fix incorrect use of dmabuf locks, and possible races with iommufd
  destroy and dmabuf revoke

- Sashiko errors found in the uAPI validation for IOMMU_HWPT_INVALIDATE

----------------------------------------------------------------
Alex Mastro (1):
      iommufd: Clarify IOAS_MAP_FILE dma-buf support

Ankit Soni (1):
      iommufd: Take dma_resv lock before dma_buf_unpin() in release path

Jason Gunthorpe (1):
      iommufd: Destroy the pages content after detaching from dmabuf

Kai Aizen (1):
      iommufd: Use sizeof(*hdr) instead of sizeof(hdr) in veventq read

Nicolin Chen (14):
      iommufd: Fix data_len byte-count vs element-count mismatch
      iommufd: Move vevent memory allocation outside spinlock
      iommufd: Set veventq_depth upper bound
      iommufd/selftest: Add boundary tests for veventq_depth
      iommufd: Rewind header length in done if iommufd_veventq_fops_read() fails
      iommufd: Reject invalid read count in iommufd_veventq_fops_read()
      iommufd: Propagate allocation failure in iommufd_veventq_deliver_fetch()
      iommufd: Reject invalid read count in iommufd_fault_fops_read()
      iommufd: Break the loop on failure in iommufd_fault_fops_read()
      iommufd: Avoid partial fault group delivery in iommufd_fault_fops_read()
      iommufd/selftest: Cover invalid read counts on vEVENTQ FD
      iommufd: Set upper bounds on cache invalidation entry_num and entry_len
      iommufd/selftest: Add invalidation entry_num and entry_len boundary tests
      iommu: Avoid copying the user array twice in the full-array copy helper

 drivers/iommu/iommufd/driver.c                   | 13 +++---
 drivers/iommu/iommufd/eventq.c                   | 36 ++++++++++++++---
 drivers/iommu/iommufd/hw_pagetable.c             | 11 ++++-
 drivers/iommu/iommufd/iommufd_private.h          |  2 +-
 drivers/iommu/iommufd/pages.c                    | 10 +++--
 include/linux/iommu.h                            |  1 +
 include/uapi/linux/iommufd.h                     | 12 ++++--
 tools/testing/selftests/iommu/iommufd.c          | 51 +++++++++++++++++++++++-
 tools/testing/selftests/iommu/iommufd_fail_nth.c |  2 +-
 tools/testing/selftests/iommu/iommufd_utils.h    | 17 ++++----
 10 files changed, 124 insertions(+), 31 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-06-17 17:31 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 17:30 Jason Gunthorpe [this message]
2026-06-17 19:40 ` [GIT PULL] Please pull IOMMUFD subsystem changes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
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=20260617173054.GA235044@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.