From: Alex Williamson <alex@shazbot.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
amastro@fb.com
Subject: [GIT PULL] VFIO update for v6.18-rc4
Date: Fri, 31 Oct 2025 14:17:47 -0600 [thread overview]
Message-ID: <20251031141747.1fd01a0a@shazbot.org> (raw)
Hi Linus,
The following changes since commit dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa:
Linux 6.18-rc3 (2025-10-26 15:59:49 -0700)
are available in the Git repository at:
https://github.com/awilliam/linux-vfio.git tags/vfio-v6.18-rc4
for you to fetch changes up to de8d1f2fd5a510bf2c1c25b84e1a718a0f0af105:
vfio: selftests: add end of address space DMA map/unmap tests (2025-10-28 15:54:41 -0600)
----------------------------------------------------------------
VFIO update for v6.18-rc4
- Fix overflows in vfio type1 backend for mappings at the end of the
64-bit address space, resulting in leaked pinned memory. New
selftest support included to avoid such issues in the future.
(Alex Mastro)
----------------------------------------------------------------
Alex Mastro (5):
vfio/type1: sanitize for overflow using check_*_overflow()
vfio/type1: move iova increment to unmap_unpin_*() caller
vfio/type1: handle DMA map/unmap up to the addressable limit
vfio: selftests: update DMA map/unmap helpers to support more test kinds
vfio: selftests: add end of address space DMA map/unmap tests
drivers/vfio/vfio_iommu_type1.c | 173 +++++++++++++--------
.../testing/selftests/vfio/lib/include/vfio_util.h | 27 +++-
tools/testing/selftests/vfio/lib/vfio_pci_device.c | 104 ++++++++++---
.../testing/selftests/vfio/vfio_dma_mapping_test.c | 95 ++++++++++-
4 files changed, 308 insertions(+), 91 deletions(-)
next reply other threads:[~2025-10-31 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 20:17 Alex Williamson [this message]
2025-10-31 21:29 ` [GIT PULL] VFIO update for v6.18-rc4 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=20251031141747.1fd01a0a@shazbot.org \
--to=alex@shazbot.org \
--cc=amastro@fb.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