Jason Gunthorpe 86624ba3b5 vfio/pci: Do vf_token checks for VFIO_DEVICE_BIND_IOMMUFD ... This was missed during the initial implementation. The VFIO PCI encodes the vf_token inside the device name when opening the device from the group FD, something like: "0000:04:10.0 vf_token=bd8d9d2b-5a5f-4f5a-a211-f591514ba1f3" This is used to control access to a VF unless there is co-ordination with the owner of the PF. Since we no longer have a device name in the cdev path, pass the token directly through VFIO_DEVICE_BIND_IOMMUFD using an optional field indicated by VFIO_DEVICE_BIND_FLAG_TOKEN. Fixes: 5fcc26969a ("vfio: Add VFIO_DEVICE_BIND_IOMMUFD") Tested-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com> Reviewed-by: Yi Liu <yi.l.liu@intel.com> Signed-off-by: Jason Gunthorpe <jgg@nvidia.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Link: https://lore.kernel.org/r/0-v3-bdd8716e85fe+3978a-vfio_token_jgg@nvidia.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>		2025-08-05 15:41:14 -06:00
..
cmd.c	vfio/mlx5: fix possible overflow in tracking max message size	2025-07-15 14:17:17 -06:00
cmd.h	vfio/mlx5: Enable the DMA link API	2025-05-20 08:32:07 -06:00
Kconfig	vfio: Move iova_bitmap into iommufd	2023-10-24 11:58:42 -03:00
main.c	vfio/pci: Do vf_token checks for VFIO_DEVICE_BIND_IOMMUFD	2025-08-05 15:41:14 -06:00
Makefile