diff options
author | Íñigo Huguet <ihuguet@redhat.com> | 2021-06-21 17:32:36 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-06-22 18:51:13 +0200 |
commit | 1ebe4feb8b442884f5a28d2437040096723dd1ea (patch) | |
tree | 08918d73857a0b33e4c7267f9029be24d4b72247 /drivers/counter | |
parent | sfc: avoid double pci_remove of VFs (diff) | |
download | linux-1ebe4feb8b442884f5a28d2437040096723dd1ea.tar.xz linux-1ebe4feb8b442884f5a28d2437040096723dd1ea.zip |
sfc: error code if SRIOV cannot be disabled
If SRIOV cannot be disabled during device removal or module unloading,
return error code so it can be logged properly in the calling function.
Note that this can only happen if any VF is currently attached to a
guest using Xen, but not with vfio/KVM. Despite that in that case the
VFs won't work properly with PF removed and/or the module unloaded, I
have let it as is because I don't know what side effects may have
changing it, and also it seems to be the same that other drivers are
doing in this situation.
In the case of being called during SRIOV reconfiguration, the behavior
hasn't changed because the function is called with force=false.
Signed-off-by: Íñigo Huguet <ihuguet@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/counter')
0 files changed, 0 insertions, 0 deletions