Re: [PATCH net v3 0/5] bonding: 3ad: fix carrier state with no valid slaves

[Jonas Gorski <jonas.gorski@gmail.com>]

On 09/04/2026 05:13, Jakub Kicinski wrote:
> On Wed,  8 Apr 2026 17:23:48 +0200 Louis Scalbert wrote:
>> The current behavior is not compliant with the LACP standard. This
>> patchset introduces a working behavior that is not strictly
>> standard-compliant either, but is widely adopted across the industry.
>> It consists of bringing the bonding master interface down to signal to
>> upper-layer processes that it is not usable.
> 
> Is the only problem the compliance? If so I don't think this qualifies
> as a fix. Please drop the Fixes tags and repost for net-next. Please
> keep in mind the 24h reposting period (also I need some time tomorrow
> to queue your patch to the CI so that the selftest passes when v4 is
> posted :()

Signalling link up too early can cause issues for some protocols that
may change behavior in the absence of PDUs from a link partner.

E.g. AFAIU RSTP may decide the bond is an edge port because no RSTP
BPDUs received and put the bond in forwarding, which then temporarily
creates a loop once the bond actually starts forwarding packets (until
it receives the next RSTP BPDU, which may take up to two seconds).

Best regards,
Jonas