From: Jay Vosburgh <jv@jvosburgh.net>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Louis Scalbert <louis.scalbert@6wind.com>,
netdev@vger.kernel.org, andrew+netdev@lunn.ch,
edumazet@google.com, kuba@kernel.org, fbl@redhat.com,
andy@greyhouse.net, shemminger@vyatta.com, maheshb@google.com,
jonas.gorski@gmail.com, horms@kernel.org
Subject: Re: [PATCH net v8 4/6] bonding: 3ad: fix carrier when no usable slaves
Date: Tue, 09 Jun 2026 21:01:45 -0700 [thread overview]
Message-ID: <1120239.1781064105@famine> (raw)
In-Reply-To: <377b117a-b29a-4761-aae0-3236be1f0b49@redhat.com>
Paolo Abeni <pabeni@redhat.com> wrote:
>On 6/9/26 9:56 AM, Louis Scalbert wrote:
>> Le lun. 8 juin 2026 à 23:37, Jay Vosburgh <jv@jvosburgh.net> a écrit :
>>>> @@ -1179,10 +1194,10 @@ static void ad_mux_machine(struct port *port, bool *update_slave_arr)
>>>> switch (port->sm_mux_state) {
>>>> case AD_MUX_DETACHED:
>>>> port->actor_oper_port_state &= ~LACP_STATE_SYNCHRONIZATION;
>>>> - ad_disable_collecting_distributing(port,
>>>> - update_slave_arr);
>>>> port->actor_oper_port_state &= ~LACP_STATE_COLLECTING;
>>>> port->actor_oper_port_state &= ~LACP_STATE_DISTRIBUTING;
>>>> + ad_disable_collecting_distributing(port,
>>>> + update_slave_arr);
>>>
>>> Is there a functional reason to move this? I don't see anything
>>> obvious in ad_disable_collecting_distributing() that depends on the
>>> actor_oper_port_state. Since you want this to be backported via stable,
>>> fewer actual changes reduce the chances of an issue applying the patch
>>> to an older version.
>>
>> The path is ad_disable_collecting_distributing() ->
>> bond_3ad_set_carrier() -> __agg_usable_ports(). __agg_usable_ports()
>> reads port->actor_oper_port_state
>>
>> It was found by
>> https://sashiko.dev/#/message/20260526084048.1696544-5-louis.scalbert%406wind.com
>
>@Jay: it's not clear to me if you are ok with the series in the current
>shape, could you please clarify?
This was the last question I had; everything in this version
seems reasonable.
For the series:
Acked-by: Jay Vosburgh <jv@jvosburgh.net>
-J
>Thanks,
>
>Paolo
>
---
-Jay Vosburgh, jv@jvosburgh.net
next prev parent reply other threads:[~2026-06-10 4:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 15:03 [PATCH net v8 0/6] bonding: 3ad: fix carrier state with no usable slaves Louis Scalbert
2026-06-03 15:03 ` [PATCH net v8 1/6] tools: missed broadcast_neigh if_link uapi header Louis Scalbert
2026-06-08 21:16 ` Jay Vosburgh
2026-06-08 21:20 ` Jay Vosburgh
2026-06-03 15:03 ` [PATCH net v8 2/6] netlink: specs: rt-link: missed broadcast-neigh Louis Scalbert
2026-06-03 15:03 ` [PATCH net v8 3/6] bonding: 3ad: add lacp_strict configuration knob Louis Scalbert
2026-06-03 15:03 ` [PATCH net v8 4/6] bonding: 3ad: fix carrier when no usable slaves Louis Scalbert
2026-06-08 21:37 ` Jay Vosburgh
2026-06-09 7:56 ` Louis Scalbert
2026-06-09 8:54 ` Paolo Abeni
2026-06-10 4:01 ` Jay Vosburgh [this message]
2026-06-03 15:03 ` [PATCH net v8 5/6] bonding: 3ad: fix mux port state on oper down Louis Scalbert
2026-06-03 15:03 ` [PATCH net v8 6/6] selftests: bonding: add test for lacp_strict mode Louis Scalbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1120239.1781064105@famine \
--to=jv@jvosburgh.net \
--cc=andrew+netdev@lunn.ch \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=fbl@redhat.com \
--cc=horms@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=louis.scalbert@6wind.com \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shemminger@vyatta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox