Re: [PATCH net v3] bonding: fix initial last_rx vs ARP-monitor slack window

[Ramses]

Oct 28, 2026, 13:25 by netdev-bot+sashiko@xxxxxxxxxx:

>
> [Severity: Medium]
> Just after this hunk, bond_enslave() copies the same value into last_tx:
>
>  new_slave->last_tx = new_slave->last_rx;
>
> So last_tx now also starts two intervals old. Could that cause a spurious
> UP->DOWN transition in bond_loadbalance_arp_mon(), used by balance-rr,
> balance-xor and broadcast with arp_interval set?
>
>
This has already been fixed in v4 of this patch series which I sent this morning.

v4 only uses the older seed for a slave that starts DOWN, and patch 2 of v4 seeds a slave that starts UP with last_link_up, so last_tx gets a full arp_missed_max window too.

See: https://lore.kernel.org/netdev/20261028-bonding-last-rx-v4-0-4d8e4cd47467@xxxxxxxxxxxxxxxx/

Ramses