diff options
author | Alex Williamson | 2018-07-13 00:33:04 +0200 |
---|---|---|
committer | Alex Williamson | 2018-08-06 20:23:19 +0200 |
commit | 0dd0e297f0ec780b6b3484ba38b27d18c8ca7af9 (patch) | |
tree | 7ca25cc8284c0a53355f710582cc3b66f2f1905a /arch/s390/purgatory/head.S | |
parent | vfio: Mark expected switch fall-throughs (diff) | |
download | kernel-qcow2-linux-0dd0e297f0ec780b6b3484ba38b27d18c8ca7af9.tar.gz kernel-qcow2-linux-0dd0e297f0ec780b6b3484ba38b27d18c8ca7af9.tar.xz kernel-qcow2-linux-0dd0e297f0ec780b6b3484ba38b27d18c8ca7af9.zip |
vfio-pci: Disable binding to PFs with SR-IOV enabled
We expect to receive PFs with SR-IOV disabled, however some host
drivers leave SR-IOV enabled at unbind. This puts us in a state where
we can potentially assign both the PF and the VF, leading to both
functionality as well as security concerns due to lack of managing the
SR-IOV state as well as vendor dependent isolation from the PF to VF.
If we were to attempt to actively disable SR-IOV on driver probe, we
risk VF bound drivers blocking, potentially risking live lock
scenarios. Therefore simply refuse to bind to PFs with SR-IOV enabled
with a warning message indicating the issue. Users can resolve this
by re-binding to the host driver and disabling SR-IOV before
attempting to use the device with vfio-pci.
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'arch/s390/purgatory/head.S')
0 files changed, 0 insertions, 0 deletions