mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Auger Eric <eric.auger@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] vfio: Create interface for vfio bus drivers to register
Date: Wed, 14 Jun 2017 15:17:25 +0200	[thread overview]
Message-ID: <be8e0633-c33d-ff08-fa44-85a5db3f68c0@redhat.com> (raw)
In-Reply-To: <20170609220011.31986.88036.stgit@gimli.home>

Hi,

On 10/06/2017 00:00, Alex Williamson wrote:
> Generally we don't know about vfio bus drivers until a device is
> added to the vfio-core with vfio_add_group_dev(), this optional
> registration with vfio_register_bus_driver() allows vfio-core to
> track known drivers.  Our current use for this information is to
> know whether a driver is vfio compatible during a bind operation.
> For devices on buses with driver_override support, we can use this
> linkage to block non-vfio drivers from binding to devices where
> the iommu group state would trigger a BUG to avoid host/user
> integrity issues.
> 
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Reviewed-by: Eric Auger <eric.auger@redhat.com>

Thanks

Eric
> ---
>  drivers/vfio/vfio.c  |   55 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  include/linux/vfio.h |    3 +++
>  2 files changed, 58 insertions(+)
> 
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index e6117de60f87..a25ee4930200 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -43,6 +43,8 @@
>  	struct class			*class;
>  	struct list_head		iommu_drivers_list;
>  	struct mutex			iommu_drivers_lock;
> +	struct list_head		bus_drivers_list;
> +	struct mutex			bus_drivers_lock;
>  	struct list_head		group_list;
>  	struct idr			group_idr;
>  	struct mutex			group_lock;
> @@ -51,6 +53,11 @@
>  	wait_queue_head_t		release_q;
>  } vfio;
>  
> +struct vfio_bus_driver {
> +	struct device_driver		*drv;
> +	struct list_head		vfio_next;
> +};
> +
>  struct vfio_iommu_driver {
>  	const struct vfio_iommu_driver_ops	*ops;
>  	struct list_head			vfio_next;
> @@ -2243,6 +2250,52 @@ int vfio_unregister_notifier(struct device *dev, enum vfio_notify_type type,
>  }
>  EXPORT_SYMBOL(vfio_unregister_notifier);
>  
> +int vfio_register_bus_driver(struct device_driver *drv)
> +{
> +	struct vfio_bus_driver *driver, *tmp;
> +
> +	driver = kzalloc(sizeof(*driver), GFP_KERNEL);
> +	if (!driver)
> +		return -ENOMEM;
> +
> +	driver->drv = drv;
> +
> +	mutex_lock(&vfio.bus_drivers_lock);
> +
> +	/* Check for duplicates */
> +	list_for_each_entry(tmp, &vfio.bus_drivers_list, vfio_next) {
> +		if (tmp->drv == drv) {
> +			mutex_unlock(&vfio.bus_drivers_lock);
> +			kfree(driver);
> +			return -EINVAL;
> +		}
> +	}
> +
> +	list_add(&driver->vfio_next, &vfio.bus_drivers_list);
> +
> +	mutex_unlock(&vfio.bus_drivers_lock);
> +
> +	return 0;
> +}
> +EXPORT_SYMBOL_GPL(vfio_register_bus_driver);
> +
> +void vfio_unregister_bus_driver(struct device_driver *drv)
> +{
> +	struct vfio_bus_driver *driver;
> +
> +	mutex_lock(&vfio.bus_drivers_lock);
> +	list_for_each_entry(driver, &vfio.bus_drivers_list, vfio_next) {
> +		if (driver->drv == drv) {
> +			list_del(&driver->vfio_next);
> +			mutex_unlock(&vfio.bus_drivers_lock);
> +			kfree(driver);
> +			return;
> +		}
> +	}
> +	mutex_unlock(&vfio.bus_drivers_lock);
> +}
> +EXPORT_SYMBOL_GPL(vfio_unregister_bus_driver);
> +
>  /**
>   * Module/class support
>   */
> @@ -2266,8 +2319,10 @@ static int __init vfio_init(void)
>  	idr_init(&vfio.group_idr);
>  	mutex_init(&vfio.group_lock);
>  	mutex_init(&vfio.iommu_drivers_lock);
> +	mutex_init(&vfio.bus_drivers_lock);
>  	INIT_LIST_HEAD(&vfio.group_list);
>  	INIT_LIST_HEAD(&vfio.iommu_drivers_list);
> +	INIT_LIST_HEAD(&vfio.bus_drivers_list);
>  	init_waitqueue_head(&vfio.release_q);
>  
>  	ret = misc_register(&vfio_dev);
> diff --git a/include/linux/vfio.h b/include/linux/vfio.h
> index 9b34d0af5d27..dab0f8105e4a 100644
> --- a/include/linux/vfio.h
> +++ b/include/linux/vfio.h
> @@ -92,6 +92,9 @@ struct vfio_iommu_driver_ops {
>  extern void vfio_unregister_iommu_driver(
>  				const struct vfio_iommu_driver_ops *ops);
>  
> +extern int vfio_register_bus_driver(struct device_driver *drv);
> +extern void vfio_unregister_bus_driver(struct device_driver *drv);
> +
>  /*
>   * External user API
>   */
> 

  reply	other threads:[~2017-06-14 13:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09 21:59 [PATCH 0/7] vfio: Fix release ordering races and use driver_override Alex Williamson
2017-06-09 21:59 ` [PATCH 1/7] vfio: Fix group release deadlock Alex Williamson
2017-06-14 12:31   ` Auger Eric
2017-06-09 21:59 ` [PATCH 2/7] kvm-vfio: Decouple only when we match a group Alex Williamson
2017-06-12 16:28   ` Paolo Bonzini
2017-06-14 12:31   ` Auger Eric
2017-06-09 21:59 ` [PATCH 3/7] vfio: New external user group/file match Alex Williamson
2017-06-12 16:27   ` Paolo Bonzini
2017-06-14 12:42   ` Auger Eric
2017-06-09 21:59 ` [PATCH 4/7] iommu: Add driver-not-bound notification Alex Williamson
2017-06-09 22:21   ` Joerg Roedel
2017-06-09 22:43     ` Alex Williamson
2017-06-10 21:39       ` Joerg Roedel
2017-06-14 12:52   ` Auger Eric
2017-06-09 22:00 ` [PATCH 5/7] vfio: Create interface for vfio bus drivers to register Alex Williamson
2017-06-14 13:17   ` Auger Eric [this message]
2017-06-09 22:00 ` [PATCH 6/7] vfio: Register pci, platform, amba, and mdev bus drivers Alex Williamson
2017-06-14 13:17   ` Auger Eric
2017-06-09 22:00 ` [PATCH 7/7] vfio: Use driver_override to avert binding to compromising drivers Alex Williamson
2017-06-19 14:03   ` Auger Eric

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=be8e0633-c33d-ff08-fa44-85a5db3f68c0@redhat.com \
    --to=eric.auger@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®