From: Leon Romanovsky <leon@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: "Jason Gunthorpe" <jgg@nvidia.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
"Jens Axboe" <axboe@kernel.dk>, "Joerg Roedel" <joro@8bytes.org>,
kvm@vger.kernel.org, linaro-mm-sig@lists.linaro.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-mm@kvack.org,
linux-pci@vger.kernel.org,
"Logan Gunthorpe" <logang@deltatee.com>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
"Will Deacon" <will@kernel.org>
Subject: Re: [PATCH v4 10/10] vfio/pci: Add dma-buf export support for MMIO regions
Date: Tue, 30 Sep 2025 12:00:48 +0300 [thread overview]
Message-ID: <20250930090048.GG324804@unreal> (raw)
In-Reply-To: <20250929151749.2007b192.alex.williamson@redhat.com>
On Mon, Sep 29, 2025 at 03:17:49PM -0600, Alex Williamson wrote:
> On Sun, 28 Sep 2025 17:50:20 +0300
> Leon Romanovsky <leon@kernel.org> wrote:
> > +static int validate_dmabuf_input(struct vfio_pci_core_device *vdev,
> > + struct vfio_device_feature_dma_buf *dma_buf,
> > + struct vfio_region_dma_range *dma_ranges,
> > + struct p2pdma_provider **provider)
> > +{
> > + struct pci_dev *pdev = vdev->pdev;
> > + u32 bar = dma_buf->region_index;
> > + resource_size_t bar_size;
> > + u64 sum;
> > + int i;
> > +
> > + if (dma_buf->flags)
> > + return -EINVAL;
> > + /*
> > + * For PCI the region_index is the BAR number like everything else.
> > + */
> > + if (bar >= VFIO_PCI_ROM_REGION_INDEX)
> > + return -ENODEV;
> > +
> > + *provider = pcim_p2pdma_provider(pdev, bar);
> > + if (!provider)
>
> This needs to be IS_ERR_OR_NULL() or the function needs to settle on a
> consistent error return value regardless of CONFIG_PCI_P2PDMA.
pcim_p2pdma_provider() doesn't return errors after split to _init() and _get().
The more accurate check needs to be if (!*provider) and not what is written.
>
> > + return -EINVAL;
> > +
> > + bar_size = pci_resource_len(pdev, bar);
>
> We get to this feature via vfio_pci_core_ioctl_feature(), which is used
> by several variant drivers, some of which mangle the BAR size exposed
> to the user, ex. hisi_acc. I'm afraid this might actually be giving
> dmabuf access to a portion of the BAR that isn't exposed otherwise.
Doe you mean that part?
1185 static int hisi_acc_vf_qm_init(struct hisi_acc_vf_core_device *hisi_acc_vdev)
1186 {
...
1204 * Also the HiSilicon ACC VF devices supported by this driver on
1205 * HiSilicon hardware platforms are integrated end point devices
1206 * and the platform lacks the capability to perform any PCIe P2P
1207 * between these devices.
1208 */
1209
1210 vf_qm->io_base =
1211 ioremap(pci_resource_start(vf_dev, VFIO_PCI_BAR2_REGION_INDEX),
1212 pci_resource_len(vf_dev, VFIO_PCI_BAR2_REGION_INDEX));
1213 if (!vf_qm->io_base)
1214 return -EIO;
1215
According to the comment, it doesn't support p2p and in any case we will
fail that platform in vfio_pci_dma_buf_attach() by taking "default" case:
34 switch (pci_p2pdma_map_type(priv->provider, attachment->dev)) {
35 case PCI_P2PDMA_MAP_THRU_HOST_BRIDGE:
36 break;
37 case PCI_P2PDMA_MAP_BUS_ADDR:
38 /*
39 * There is no need in IOVA at all for this flow.
40 * We rely on attachment->priv == NULL as a marker
41 * for this mode.
42 */
43 return 0;
44 default:
45 return -EINVAL;
46 }
47
>
> > + for (i = 0; i < dma_buf->nr_ranges; i++) {
> > + u64 offset = dma_ranges[i].offset;
> > + u64 len = dma_ranges[i].length;
> > +
> > + if (!PAGE_ALIGNED(offset) || !PAGE_ALIGNED(len))
> > + return -EINVAL;
> > +
> > + if (check_add_overflow(offset, len, &sum) || sum > bar_size)
> > + return -EINVAL;
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +int vfio_pci_core_feature_dma_buf(struct vfio_pci_core_device *vdev, u32 flags,
> > + struct vfio_device_feature_dma_buf __user *arg,
> > + size_t argsz)
> > +{
> > + struct vfio_device_feature_dma_buf get_dma_buf = {};
> > + struct vfio_region_dma_range *dma_ranges;
> > + DEFINE_DMA_BUF_EXPORT_INFO(exp_info);
> > + struct p2pdma_provider *provider;
> > + struct vfio_pci_dma_buf *priv;
> > + int ret;
> > +
> > + ret = vfio_check_feature(flags, argsz, VFIO_DEVICE_FEATURE_GET,
> > + sizeof(get_dma_buf));
> > + if (ret != 1)
> > + return ret;
> > +
> > + if (copy_from_user(&get_dma_buf, arg, sizeof(get_dma_buf)))
> > + return -EFAULT;
> > +
> > + if (!get_dma_buf.nr_ranges)
> > + return -EINVAL;
> > +
> > + dma_ranges = memdup_array_user(&arg->dma_ranges, get_dma_buf.nr_ranges,
> > + sizeof(*dma_ranges));
> > + if (IS_ERR(dma_ranges))
> > + return PTR_ERR(dma_ranges);
> > +
> > + ret = validate_dmabuf_input(vdev, &get_dma_buf, dma_ranges, &provider);
> > + if (ret)
> > + return ret;
>
> goto err_free_ranges;
Thanks
>
> Thanks,
> Alex
>
>
next prev parent reply other threads:[~2025-09-30 9:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 14:50 [PATCH v4 00/10] vfio/pci: Allow MMIO regions to be exported through dma-buf Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 01/10] PCI/P2PDMA: Separate the mmap() support from the core logic Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 02/10] PCI/P2PDMA: Simplify bus address mapping API Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 03/10] PCI/P2PDMA: Refactor to separate core P2P functionality from memory allocation Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 04/10] PCI/P2PDMA: Export pci_p2pdma_map_type() function Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 05/10] types: move phys_vec definition to common header Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 06/10] vfio: Export vfio device get and put registration helpers Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 07/10] vfio/pci: Add dma-buf export config for MMIO regions Leon Romanovsky
2025-09-29 21:17 ` Alex Williamson
2025-09-30 7:57 ` Leon Romanovsky
2025-09-30 16:07 ` Alex Williamson
2025-10-01 11:39 ` Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 08/10] vfio/pci: Enable peer-to-peer DMA transactions by default Leon Romanovsky
2025-09-29 21:17 ` Alex Williamson
2025-09-30 7:30 ` Leon Romanovsky
2025-09-30 16:01 ` Alex Williamson
2025-09-28 14:50 ` [PATCH v4 09/10] vfio/pci: Share the core device pointer while invoking feature functions Leon Romanovsky
2025-09-28 14:50 ` [PATCH v4 10/10] vfio/pci: Add dma-buf export support for MMIO regions Leon Romanovsky
2025-09-29 21:17 ` Alex Williamson
2025-09-30 9:00 ` Leon Romanovsky [this message]
2025-09-30 12:50 ` Shameer Kolothum
2025-09-30 14:34 ` Jason Gunthorpe
2025-09-30 16:52 ` Alex Williamson
2025-09-30 18:04 ` Jason Gunthorpe
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=20250930090048.GG324804@unreal \
--to=leon@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=vivek.kasireddy@intel.com \
--cc=will@kernel.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