From: Alex Williamson <alex@shazbot.org>
To: Matt Evans <matt@ozlabs.org>
Cc: "Leon Romanovsky" <leon@kernel.org>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Alex Mastro" <amastro@fb.com>,
"Christian König" <christian.koenig@amd.com>,
"Kevin Tian" <kevin.tian@intel.com>,
"Pranjal Shrivastava" <praan@google.com>,
"Longfang Liu" <liulongfang@huawei.com>,
"Mahmoud Adam" <mngyadam@amazon.de>,
"David Matlack" <dmatlack@google.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Ankit Agrawal" <ankita@nvidia.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
kvm@vger.kernel.org, linux-pci@vger.kernel.org, alex@shazbot.org
Subject: Re: [PATCH v8 9/9] vfio/pci: Revoke a DMABUF on request from userspace
Date: Tue, 13 Oct 2026 17:13:43 -0600 [thread overview]
Message-ID: <20261013171343.2363e9e1@shazbot.org> (raw)
In-Reply-To: <20261006193643.76330-10-matt@ozlabs.org>
On Tue, 6 Oct 2026 20:36:37 +0100
Matt Evans <matt@ozlabs.org> wrote:
> +#ifdef CONFIG_VFIO_PCI_DMABUF
> +int vfio_pci_core_feature_dma_buf_revoke(
> + struct vfio_pci_core_device *vdev, u32 flags,
> + struct vfio_device_feature_dma_buf_revoke __user *arg,
> + size_t argsz)
> +{
> + struct vfio_device_feature_dma_buf_revoke db_revoke;
> + struct vfio_pci_dma_buf *priv;
> + struct dma_buf *dmabuf;
> + int ret;
> +
> + if (!vdev->pci_ops || !vdev->pci_ops->get_dmabuf_phys)
> + return -EOPNOTSUPP;
> +
> + ret = vfio_check_feature(flags, argsz,
> + VFIO_DEVICE_FEATURE_SET,
> + sizeof(db_revoke));
> + if (ret != 1)
> + return ret;
> +
> + if (copy_from_user(&db_revoke, arg, sizeof(db_revoke)))
> + return -EFAULT;
> +
> + dmabuf = dma_buf_get(db_revoke.dmabuf_fd);
> + if (IS_ERR(dmabuf))
> + return PTR_ERR(dmabuf);
> +
> + priv = dmabuf->priv;
> + /*
> + * Sanity-check the DMABUF is really a vfio_pci_dma_buf _and_
> + * relates to the VFIO device it was provided with.
> + *
> + * If the DMABUF relates to this vdev then priv->vdev is
> + * stable because this open fd prevents cleanup.
> + *
> + * If it relates to a different vdev, reading priv->vdev might
> + * race with a concurrent cleanup on that device. But if so,
> + * it points to a non-matching vdev or NULL and is unusable
> + * either way.
> + */
> + if (dmabuf->ops != &vfio_pci_dmabuf_ops ||
> + READ_ONCE(priv->vdev) != vdev) {
> + ret = -ENODEV;
> + goto out_put_buf;
> + }
> +
> + /*
> + * memory_lock(R) is taken to stop vfio_pci_dev_set_hot_reset()
> + * from getting it and then blocking all devices in the dev_set behind
> + * this revoke's drain.
> + */
> + down_read(&vdev->memory_lock);
> + down_write(&vdev->dmabuf_lock);
> + if (priv->status == VFIO_PCI_DMABUF_DEAD) {
> + ret = -EBADFD;
Kind of ugly to special case the condition in the caller that's already
tested in the function. Why not return an errno for this purpose?
Thanks,
Alex
> + } else {
> + vfio_pci_dma_buf_set_status(priv, VFIO_PCI_DMABUF_DEAD);
> + ret = 0;
> + }
> + up_write(&vdev->dmabuf_lock);
> + up_read(&vdev->memory_lock);
> +
> +out_put_buf:
> + dma_buf_put(dmabuf);
> +
> + return ret;
> +}
> +#endif /* CONFIG_VFIO_PCI_DMABUF */
prev parent reply other threads:[~2026-10-13 23:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 19:36 [PATCH v8 0/9] vfio/pci: Add mmap() for DMABUFs Matt Evans
2026-10-06 19:36 ` [PATCH v8 1/9] vfio/pci: Remove DMABUF export dependency on vdev->memory_lock Matt Evans
2026-10-13 23:14 ` Alex Williamson
2026-10-06 19:36 ` [PATCH v8 2/9] vfio/pci: Un-revoke DMABUFs in LOW_POWER_ENTRY_WITH_WAKEUP resume Matt Evans
2026-10-06 19:36 ` [PATCH v8 3/9] dma-buf: Provide dma_buf_set_name() Matt Evans
2026-10-07 9:22 ` Christian König
2026-10-12 6:27 ` Leon Romanovsky
2026-10-06 19:36 ` [PATCH v8 4/9] vfio/pci: Add a helper to look up PFNs for DMABUFs Matt Evans
2026-10-13 23:14 ` Alex Williamson
2026-10-06 19:36 ` [PATCH v8 5/9] vfio/pci: Add a helper to create a DMABUF for a BAR-map VMA Matt Evans
2026-10-06 19:36 ` [PATCH v8 6/9] vfio/pci: Convert BAR mmap() to use a DMABUF Matt Evans
2026-10-06 19:36 ` [PATCH v8 7/9] vfio/pci: Clean up BAR zap and revocation Matt Evans
2026-10-13 23:13 ` Alex Williamson
2026-10-06 19:36 ` [PATCH v8 8/9] vfio/pci: Support mmap() of a VFIO DMABUF Matt Evans
2026-10-13 23:13 ` Alex Williamson
2026-10-06 19:36 ` [PATCH v8 9/9] vfio/pci: Revoke a DMABUF on request from userspace Matt Evans
2026-10-13 23:13 ` 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=20261013171343.2363e9e1@shazbot.org \
--to=alex@shazbot.org \
--cc=amastro@fb.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=bjorn@kernel.org \
--cc=christian.koenig@amd.com \
--cc=dmatlack@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liulongfang@huawei.com \
--cc=matt@ozlabs.org \
--cc=mngyadam@amazon.de \
--cc=praan@google.com \
--cc=sumit.semwal@linaro.org \
--cc=vivek.kasireddy@intel.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