Re: [PATCH net v4 2/2] bonding: give a slave that starts UP a full arp_missed_max window

[Ramses]

> [Severity: High]
> Does this fix still miss the case where the ARP monitor starts some time
> after enslavement?

Yes. As the review notes, the old seed behaved the same way there, so
this is not a regression. v5 narrows the commit message to a slave
enslaved while the ARP monitor is running. Reseeding when the monitor
starts later will be a separate follow-up, see my reply on patch 1.