From: Alex Williamson <alex@shazbot.org>
To: Matt Evans <mattev@meta.com>
Cc: Kevin Tian <kevin.tian@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Ankit Agrawal <ankita@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Kees Cook <kees@kernel.org>,
Shameer Kolothum <skolothumtho@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Eric Auger <eric.auger@redhat.com>, Peter Xu <peterx@redhat.com>,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
Zhi Wang <zhiw@nvidia.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <virtualization@lists.linux.dev>,
alex@shazbot.org
Subject: Re: [PATCH v5 0/3] vfio/pci: Request resources and map BARs at enable time
Date: Thu, 14 May 2026 10:38:48 -0600 [thread overview]
Message-ID: <20260514103848.577a6e05@shazbot.org> (raw)
In-Reply-To: <20260511145829.2993601-1-mattev@meta.com>
On Mon, 11 May 2026 07:58:22 -0700
Matt Evans <mattev@meta.com> wrote:
> Hi,
>
> These patches fix a potential race for concurrent calls to
> vfio_pci_core_setup_barmap(), and a DMABUF missing check for resource
> before the export. Discussion on a previous series (different,
> replaced by this one) is here:
>
> https://lore.kernel.org/kvm/20260415181423.1008458-1-mattev@meta.com
>
> Responses in that thread indicated there wasn't a strong historical
> reason to require the mapping to be performed on-demand at BAR
> reference time. It's much simpler to move this earlier, to
> vfio_pci_core_enable(), and that then avoids having to deal with
> concurrent requests later.
>
> The first patch requests PCI resources and pci_iomap() of the BARs
> from vfio_pci_core_enable(), moving this out of
> vfio_pci_core_setup_barmap().
>
> Some callers rely on vfio_pci_core_setup_barmap() for its ioremap()
> effect, and other callers use it for its resource-acquiring effect.
> The function turns into a cheap error check that both these actions
> have occurred; that maintains the same error behaviour as before the
> fix.
>
> The second patch adds a call to vfio_pci_core_setup_barmap() to VFIO
> DMABUF export to check the resource is reserved; previously this was
> able to export an unrequested resource. Although patch 1 at first
> appears to fix this by requesting resources at enable time, code using
> the BAR still needs to check the resource really was acquired.
>
> (FWIW, Leon gave a R-B on v2 in
> https://lore.kernel.org/kvm/20260426111606.GC440345@unreal/ though
> this repost isn't 100% identical so I didn't propagate it.)
>
> The third patch refactors vfio_pci_core_setup_barmap() plus the various
> vdev->barmap[] accesses into vfio_pci_core_get_iomap() which returns
> either a pointer to the mapping or an ERR_PTR() describing why it
> doesn't exist. This is used by callers that need the mapping, but
> also by other callers to check that the resource/mapping step was
> successful.
>
> Matt Evans (3):
> vfio/pci: Set up BAR resources and maps in vfio_pci_core_enable()
> vfio/pci: Check BAR resources before exporting a DMABUF
> vfio/pci: Replace vfio_pci_core_setup_barmap() with
> vfio_pci_core_get_iomap()
>
> drivers/vfio/pci/nvgrace-gpu/main.c | 20 +++++++-----
> drivers/vfio/pci/vfio_pci_core.c | 48 ++++++++++++++++++++++++-----
> drivers/vfio/pci/vfio_pci_dmabuf.c | 6 ++--
> drivers/vfio/pci/vfio_pci_rdwr.c | 42 +++++--------------------
> drivers/vfio/pci/virtio/legacy_io.c | 13 ++++----
> include/linux/vfio_pci_core.h | 20 +++++++++++-
> 6 files changed, 91 insertions(+), 58 deletions(-)
>
Applied 1/ and 2/ to the vfio for-linus branch for v7.1-rc. My
intention is to have these merged for rc4, which I'll then use as the
base for the v7.2 queue where we can pull in 3/. Thanks,
Alex
prev parent reply other threads:[~2026-05-14 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 14:58 [PATCH v5 0/3] vfio/pci: Request resources and map BARs at enable time Matt Evans
2026-05-11 14:58 ` [PATCH v5 1/3] vfio/pci: Set up BAR resources and maps in vfio_pci_core_enable() Matt Evans
2026-05-11 14:58 ` [PATCH v5 2/3] vfio/pci: Check BAR resources before exporting a DMABUF Matt Evans
2026-05-11 14:58 ` [PATCH v5 3/3] vfio/pci: Replace vfio_pci_core_setup_barmap() with vfio_pci_core_get_iomap() Matt Evans
2026-05-14 16:38 ` Alex Williamson [this message]
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=20260514103848.577a6e05@shazbot.org \
--to=alex@shazbot.org \
--cc=aik@ozlabs.ru \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=eric.auger@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kees@kernel.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattev@meta.com \
--cc=peterx@redhat.com \
--cc=skolothumtho@nvidia.com \
--cc=virtualization@lists.linux.dev \
--cc=vivek.kasireddy@intel.com \
--cc=yishaih@nvidia.com \
--cc=zhiw@nvidia.com \
/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