summaryrefslogtreecommitdiffstats
path: root/net/phonet/pn_netlink.c
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2013-06-10 16:40:56 -0600
committerAlex Williamson <alex.williamson@redhat.com>2013-07-24 16:36:00 -0600
commitde9c7602ca25f52bbfeb52e7d85765fe70b92dce (patch)
tree7ad1108d39c1a7dbed91db60c2a63321d19da3c3 /net/phonet/pn_netlink.c
parent3b2f64d00c46e1e4e9bd0bb9bb12619adac27a4b (diff)
downloadop-kernel-dev-de9c7602ca25f52bbfeb52e7d85765fe70b92dce.zip
op-kernel-dev-de9c7602ca25f52bbfeb52e7d85765fe70b92dce.tar.gz
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 'net/phonet/pn_netlink.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud