diff options
| author | Alex Williamson <alex.williamson@redhat.com> | 2013-06-11 02:40:56 +0400 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@redhat.com> | 2013-07-25 02:36:00 +0400 |
| commit | de9c7602ca25f52bbfeb52e7d85765fe70b92dce (patch) | |
| tree | 7ad1108d39c1a7dbed91db60c2a63321d19da3c3 /drivers/leds/leds-mc13783.c | |
| parent | 3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b (diff) | |
| download | linux-de9c7602ca25f52bbfeb52e7d85765fe70b92dce.tar.xz | |
vfio: Don't overreact to DEL_DEVICE
BUS_NOTIFY_DEL_DEVICE triggers IOMMU drivers to remove devices from
their iommu group, but there's really nothing we can do about it at
this point. If the device is in use, then the vfio sub-driver will
block the device_del from completing until it's released. If the
device is not in use or not owned by a vfio sub-driver, then we
really don't care that it's being removed.
The current code can be triggered just by unloading an sr-iov driver
(ex. igb) while the VFs are attached to vfio-pci because it makes an
incorrect assumption about the ordering of driver remove callbacks
vs the DEL_DEVICE notification.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'drivers/leds/leds-mc13783.c')
0 files changed, 0 insertions, 0 deletions