mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-16 01:06:50 +07:00
266b495f11
There is presently a race condition between the bonding periodic link monitor and the updating of a slave's speed and duplex. The former occurs on a periodic basis, and the latter in response to a driver's calling of netif_carrier_on. It is possible for the periodic monitor to run between the driver call of netif_carrier_on and the receipt of the NETDEV_CHANGE event that causes bonding to update the slave's speed and duplex. This manifests most notably as a report that a slave is up and "0 Mbps full duplex" after enslavement, but in principle could report an incorrect speed and duplex after any link up event if the device comes up with a different speed or duplex. This affects the 802.3ad aggregator selection, as the speed and duplex are selection criteria. This is fixed by updating the speed and duplex in the periodic monitor, prior to using that information. This was done historically in bonding, but the call to bond_update_speed_duplex was removed in commit |
||
---|---|---|
.. | ||
bond_3ad.c | ||
bond_alb.c | ||
bond_debugfs.c | ||
bond_main.c | ||
bond_netlink.c | ||
bond_options.c | ||
bond_procfs.c | ||
bond_sysfs_slave.c | ||
bond_sysfs.c | ||
bonding_priv.h | ||
Makefile |