diff options
| author | Stephen Hemminger <stephen@networkplumber.org> | 2020-08-04 19:54:15 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-08-11 16:33:40 +0300 |
| commit | 5d791d36a49b82c7deb75db8b261d53337cafb00 (patch) | |
| tree | 9c6974aef68084356916781fe9f3601b6d8415b4 /net | |
| parent | 3a82f4bfd20a2c8a559ccae08cb0606b74036f1d (diff) | |
| download | linux-5d791d36a49b82c7deb75db8b261d53337cafb00.tar.xz | |
hv_netvsc: do not use VF device if link is down
[ Upstream commit 7c9864bbccc23e1812ac82966555d68c13ea4006 ]
If the accelerated networking SRIOV VF device has lost carrier
use the synthetic network device which is available as backup
path. This is a rare case since if VF link goes down, normally
the VMBus device will also loose external connectivity as well.
But if the communication is between two VM's on the same host
the VMBus device will still work.
Reported-by: "Shah, Ashish N" <ashish.n.shah@intel.com>
Fixes: 0c195567a8f6 ("netvsc: transparent VF management")
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions