From: Alex Williamson <alex@shazbot.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: alex@shazbot.org, "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] VFIO fixes for v7.1-rc4
Date: Fri, 15 May 2026 11:22:41 -0600 [thread overview]
Message-ID: <20260515112241.39f9df48@shazbot.org> (raw)
Hi Linus,
Please include for rc4. Thanks!
The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:
Linux 7.1-rc3 (2026-05-10 14:08:09 -0700)
are available in the Git repository at:
https://github.com/awilliam/linux-vfio.git tags/vfio-v7.1-rc4
for you to fetch changes up to 702809dabdecca807bdd50cfdcc1c980feb2ba62:
vfio/pci: Check BAR resources before exporting a DMABUF (2026-05-14 11:39:03 -0600)
----------------------------------------------------------------
VFIO fixes for v7.1-rc4
- Convert vfio-pci BAR resource requests and iomaps initialization
from a lazy, on-demand model to an eager pre-allocation model to
avoid races while preserving legacy error behavior. Fix unchecked
barmap access in dma-buf export path. (Matt Evans)
- Introduce an implicit unsigned cast in converting vfio-pci device
offsets to region indexes, closing a potential out-of-bounds
access through the vfio_pci_ioeventfd() interface. (Matt Evans)
- Fix a dma-buf kref underflow and stuck wait_for_completion() when
closing a previously revoked dma-buf. (Alex Williamson)
----------------------------------------------------------------
Alex Williamson (1):
vfio/pci: fix dma-buf kref underflow after revoke
Matt Evans (3):
vfio/pci: Make VFIO_PCI_OFFSET_TO_INDEX() return unsigned
vfio/pci: Set up BAR resources and maps in vfio_pci_core_enable()
vfio/pci: Check BAR resources before exporting a DMABUF
drivers/vfio/pci/vfio_pci_core.c | 37 ++++++++++++++++++++++++++++++++-
drivers/vfio/pci/vfio_pci_dmabuf.c | 42 ++++++++++++++++++++------------------
drivers/vfio/pci/vfio_pci_rdwr.c | 26 +++++++----------------
include/linux/vfio_pci_core.h | 2 +-
4 files changed, 66 insertions(+), 41 deletions(-)
reply other threads:[~2026-05-15 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260515112241.39f9df48@shazbot.org \
--to=alex@shazbot.org \
--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