lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Thu, 16 Dec 2021 17:20:21 +0200
From:   Leonid Bloch <leonidb@...cscloud.com>
To:     Jesse Brandeburg <jesse.brandeburg@...el.com>,
        Tony Nguyen <anthony.l.nguyen@...el.com>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Stefan Assmann <sassmann@...nic.de>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        netdev@...r.kernel.org, intel-wired-lan@...ts.osuosl.org
Subject: PROBLEM: iavf seems not to fully bind to all the devices all the time

Hi,

I have a VM with 3 Intel VF's attached:

# lspci | grep Ethernet
04:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)
0b:00.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 
700 Series (rev 04)
13:00.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 
700 Series (rev 04)
1b:00.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 
700 Series (rev 04)

But not on every boot or driver load/unload all the VFs are fully 
initialized (some do not appear as network interfaces):

# ip l | sed '/^[0-9]\+:/! d' | bc <<<"$(wc -l) - 2"
3
# rmmod iavf
# modprobe iavf
# ip l | sed '/^[0-9]\+:/! d' | bc <<<"$(wc -l) - 2"
1
# rmmod iavf
# modprobe iavf
# ip l | sed '/^[0-9]\+:/! d' | bc <<<"$(wc -l) - 2"
3

...etc (the number always varies between 3 - all the interfaces, and 1 - 
only one interface, never 0).

The PCI devices which do not appear as network interfaces however, still 
appear as bound to iavf, but somehow not fully:

When all the interfaces appear:
# lshw | grep iavf
configuration: autonegotiation=off broadcast=yes driver=iavf 
driverversion=5.10.78.rt56-1 duplex=full firmware=N/A latency=64 link=no 
multicast=yes
configuration: autonegotiation=off broadcast=yes driver=iavf 
driverversion=5.10.78.rt56-1 duplex=full firmware=N/A latency=64 link=no 
multicast=yes
configuration: autonegotiation=off broadcast=yes driver=iavf 
driverversion=5.10.78.rt56-1 duplex=full firmware=N/A latency=64 link=no 
multicast=yes

When only 2/3 appear:
# lshw | grep iavf
configuration: autonegotiation=off broadcast=yes driver=iavf 
driverversion=5.10.78.rt56-1 duplex=full firmware=N/A latency=64 link=no 
multicast=yes
configuration: driver=iavf latency=64
configuration: autonegotiation=off broadcast=yes driver=iavf 
driverversion=5.10.78.rt56-1 duplex=full firmware=N/A latency=64 link=no 
multicast=yes

There are no apparent errors in dmesg.

The kernels used: 5.15.7, 5.15.3, 5.15.2, 5.10.78, 5.10.56 (the ones I 
tried so far).

Any suggestions?


Thanks,
Leonid.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ