| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20220503111124.38b07a9e.alex.williamson@redhat.com>
Date: Tue, 3 May 2022 11:11:24 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: Abhishek Sahu <abhsahu@...dia.com>
Cc: Cornelia Huck <cohuck@...hat.com>,
Yishai Hadas <yishaih@...dia.com>,
Jason Gunthorpe <jgg@...dia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>,
Kevin Tian <kevin.tian@...el.com>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Max Gurtovoy <mgurtovoy@...dia.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
<linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <linux-pci@...r.kernel.org>
Subject: Re: [PATCH v3 4/8] vfio/pci: Add support for setting driver data
inside core layer
On Mon, 25 Apr 2022 14:56:11 +0530
Abhishek Sahu <abhsahu@...dia.com> wrote:
> The vfio driver is divided into two layers: core layer (implemented in
> vfio_pci_core.c) and parent driver (For example, vfio_pci, mlx5_vfio_pci,
> hisi_acc_vfio_pci, etc.). All the parent driver calls dev_set_drvdata()
> and assigns its own structure as driver data. Some of the callback
> functions are implemented in the core layer and these callback functions
> provide the reference of 'struct pci_dev' or 'struct device'. Currently,
> we use vfio_device_get_from_dev() which provides reference to the
> vfio_device for a device. But this function follows long path to extract
> the same. There are few cases, where we don't need to go through this
> long path if we get this through drvdata.
>
> This patch moves the setting of drvdata inside the core layer. If we see
> the current implementation of parent driver structure implementation,
> then 'struct vfio_pci_core_device' is a first member so the pointer of
> the parent structure and 'struct vfio_pci_core_device' should be the same.
>
> struct hisi_acc_vf_core_device {
> struct vfio_pci_core_device core_device;
> ...
> };
>
> struct mlx5vf_pci_core_device {
> struct vfio_pci_core_device core_device;
> ...
> };
>
> The vfio_pci.c uses 'struct vfio_pci_core_device' itself.
>
> To support getting the drvdata in both the layers, we can put the
> restriction to make 'struct vfio_pci_core_device' as a first member.
> Also, vfio_pci_core_register_device() has this validation which makes sure
> that this prerequisite is always satisfied.
>
> Signed-off-by: Abhishek Sahu <abhsahu@...dia.com>
> ---
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 4 ++--
> drivers/vfio/pci/mlx5/main.c | 3 +--
> drivers/vfio/pci/vfio_pci.c | 4 ++--
> drivers/vfio/pci/vfio_pci_core.c | 24 ++++++++++++++++---
> include/linux/vfio_pci_core.h | 7 +++++-
> 5 files changed, 32 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> index 767b5d47631a..c76c09302a8f 100644
> --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> @@ -1274,11 +1274,11 @@ static int hisi_acc_vfio_pci_probe(struct pci_dev *pdev, const struct pci_device
> &hisi_acc_vfio_pci_ops);
> }
>
> - ret = vfio_pci_core_register_device(&hisi_acc_vdev->core_device);
> + ret = vfio_pci_core_register_device(&hisi_acc_vdev->core_device,
> + hisi_acc_vdev);
> if (ret)
> goto out_free;
>
> - dev_set_drvdata(&pdev->dev, hisi_acc_vdev);
> return 0;
>
> out_free:
> diff --git a/drivers/vfio/pci/mlx5/main.c b/drivers/vfio/pci/mlx5/main.c
> index bbec5d288fee..8689248f66f3 100644
> --- a/drivers/vfio/pci/mlx5/main.c
> +++ b/drivers/vfio/pci/mlx5/main.c
> @@ -614,11 +614,10 @@ static int mlx5vf_pci_probe(struct pci_dev *pdev,
> }
> }
>
> - ret = vfio_pci_core_register_device(&mvdev->core_device);
> + ret = vfio_pci_core_register_device(&mvdev->core_device, mvdev);
> if (ret)
> goto out_free;
>
> - dev_set_drvdata(&pdev->dev, mvdev);
> return 0;
>
> out_free:
> diff --git a/drivers/vfio/pci/vfio_pci.c b/drivers/vfio/pci/vfio_pci.c
> index 2b047469e02f..e0f8027c5cd8 100644
> --- a/drivers/vfio/pci/vfio_pci.c
> +++ b/drivers/vfio/pci/vfio_pci.c
> @@ -151,10 +151,10 @@ static int vfio_pci_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> return -ENOMEM;
> vfio_pci_core_init_device(vdev, pdev, &vfio_pci_ops);
>
> - ret = vfio_pci_core_register_device(vdev);
> + ret = vfio_pci_core_register_device(vdev, vdev);
> if (ret)
> goto out_free;
> - dev_set_drvdata(&pdev->dev, vdev);
> +
> return 0;
>
> out_free:
> diff --git a/drivers/vfio/pci/vfio_pci_core.c b/drivers/vfio/pci/vfio_pci_core.c
> index 1271728a09db..953ac33b2f5f 100644
> --- a/drivers/vfio/pci/vfio_pci_core.c
> +++ b/drivers/vfio/pci/vfio_pci_core.c
> @@ -1822,9 +1822,11 @@ void vfio_pci_core_uninit_device(struct vfio_pci_core_device *vdev)
> }
> EXPORT_SYMBOL_GPL(vfio_pci_core_uninit_device);
>
> -int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev)
> +int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev,
> + void *driver_data)
> {
> struct pci_dev *pdev = vdev->pdev;
> + struct device *dev = &pdev->dev;
> int ret;
>
> if (pdev->hdr_type != PCI_HEADER_TYPE_NORMAL)
> @@ -1843,6 +1845,17 @@ int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev)
> return -EBUSY;
> }
>
> + /*
> + * The 'struct vfio_pci_core_device' should be the first member of the
> + * of the structure referenced by 'driver_data' so that it can be
> + * retrieved with dev_get_drvdata() inside vfio-pci core layer.
> + */
> + if ((struct vfio_pci_core_device *)driver_data != vdev) {
> + pci_warn(pdev, "Invalid driver data\n");
> + return -EINVAL;
> + }
It seems a bit odd to me to add a driver_data arg to the function,
which is actually required to point to the same thing as the existing
function arg. Is this just to codify the requirement? Maybe others
can suggest alternatives.
We also need to collaborate with Jason's patch:
https://lore.kernel.org/all/0-v2-0f36bcf6ec1e+64d-vfio_get_from_dev_jgg@nvidia.com/
(and maybe others)
If we implement a change like proposed here that vfio-pci-core sets
drvdata then we don't need for each variant driver to implement their
own wrapper around err_handler or err_detected as Jason proposes in the
linked patch. Thanks,
Alex
> + dev_set_drvdata(dev, driver_data);
> +
> if (pci_is_root_bus(pdev->bus)) {
> ret = vfio_assign_device_set(&vdev->vdev, vdev);
> } else if (!pci_probe_reset_slot(pdev->slot)) {
> @@ -1856,10 +1869,10 @@ int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev)
> }
>
> if (ret)
> - return ret;
> + goto out_drvdata;
> ret = vfio_pci_vf_init(vdev);
> if (ret)
> - return ret;
> + goto out_drvdata;
> ret = vfio_pci_vga_init(vdev);
> if (ret)
> goto out_vf;
> @@ -1890,6 +1903,8 @@ int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev)
> vfio_pci_set_power_state(vdev, PCI_D0);
> out_vf:
> vfio_pci_vf_uninit(vdev);
> +out_drvdata:
> + dev_set_drvdata(dev, NULL);
> return ret;
> }
> EXPORT_SYMBOL_GPL(vfio_pci_core_register_device);
> @@ -1897,6 +1912,7 @@ EXPORT_SYMBOL_GPL(vfio_pci_core_register_device);
> void vfio_pci_core_unregister_device(struct vfio_pci_core_device *vdev)
> {
> struct pci_dev *pdev = vdev->pdev;
> + struct device *dev = &pdev->dev;
>
> vfio_pci_core_sriov_configure(pdev, 0);
>
> @@ -1907,6 +1923,8 @@ void vfio_pci_core_unregister_device(struct vfio_pci_core_device *vdev)
>
> if (!disable_idle_d3)
> vfio_pci_set_power_state(vdev, PCI_D0);
> +
> + dev_set_drvdata(dev, NULL);
> }
> EXPORT_SYMBOL_GPL(vfio_pci_core_unregister_device);
>
> diff --git a/include/linux/vfio_pci_core.h b/include/linux/vfio_pci_core.h
> index 505b2a74a479..3c7d65e68340 100644
> --- a/include/linux/vfio_pci_core.h
> +++ b/include/linux/vfio_pci_core.h
> @@ -225,7 +225,12 @@ void vfio_pci_core_close_device(struct vfio_device *core_vdev);
> void vfio_pci_core_init_device(struct vfio_pci_core_device *vdev,
> struct pci_dev *pdev,
> const struct vfio_device_ops *vfio_pci_ops);
> -int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev);
> +/*
> + * The 'struct vfio_pci_core_device' should be the first member
> + * of the structure referenced by 'driver_data'.
> + */
> +int vfio_pci_core_register_device(struct vfio_pci_core_device *vdev,
> + void *driver_data);
> void vfio_pci_core_uninit_device(struct vfio_pci_core_device *vdev);
> void vfio_pci_core_unregister_device(struct vfio_pci_core_device *vdev);
> int vfio_pci_core_sriov_configure(struct pci_dev *pdev, int nr_virtfn);
Powered by blists - more mailing lists