From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
Simon Horman <horms@kernel.org>,
Mahesh Bandewar <maheshb@google.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues
Date: Mon, 2 Feb 2026 01:14:55 +0000 [thread overview]
Message-ID: <aX_6jyAQaDoqsR3G@fedora> (raw)
In-Reply-To: <20260114064921.57686-1-liuhangbin@gmail.com>
Hi Jakub, Paolo,
Is there anything I should do for this patchset ?
Thanks
Hangbin
On Wed, Jan 14, 2026 at 06:49:18AM +0000, Hangbin Liu wrote:
> This series fixes two issues in the bonding 802.3ad implementation
> related to port state management and churn detection:
>
> 1. When disabling a port, we need to set AD_RX_PORT_DISABLED to ensure
> proper state machine transitions, preventing ports from getting stuck
> in AD_RX_CURRENT state.
>
> 2. The ad_churn_machine implementation is restructured to follow IEEE
> 802.1AX-2014 specifications correctly. The current implementation has
> several issues: it doesn't transition to "none" state immediately when
> synchronization is achieved, and can get stuck in churned state in
> multi-aggregator scenarios.
>
> 3. Selftests are enhanced to validate both mux state machine and churn
> state logic under aggregator selection and failover scenarios.
>
> These changes ensure proper LACP state machine behavior and fix issues
> where ports could remain in incorrect states during aggregator failover.
>
>
> v2:
> * The changes are large and not urgent. Post to net-next as Paolo suggested
> * set AD_RX_PORT_DISABLED only in ad_agg_selection_logic to avoid side effect. (Paolo Abeni)
> * remove actor_churn as it can only be true when the state is ACTOR_CHURN (Paolo Abeni)
> * remove AD_PORT_CHURNED since we don't need it anywhere (Paolo Abeni)
> * I didn't add new helper for ad_churn_machine() as it looks not help much.
>
> v1: https://lore.kernel.org/netdev/20251124043310.34073-1-liuhangbin@gmail.com
>
> Hangbin Liu (3):
> bonding: set AD_RX_PORT_DISABLED when disabling a port
> bonding: restructure ad_churn_machine
> selftests: bonding: add mux and churn state testing
>
> drivers/net/bonding/bond_3ad.c | 97 ++++++++++++++-----
> .../selftests/drivers/net/bonding/Makefile | 2 +-
> ...nd_lacp_prio.sh => bond_lacp_ad_select.sh} | 73 ++++++++++++++
> 3 files changed, 146 insertions(+), 26 deletions(-)
> rename tools/testing/selftests/drivers/net/bonding/{bond_lacp_prio.sh => bond_lacp_ad_select.sh} (64%)
>
> --
> 2.50.1
>
next prev parent reply other threads:[~2026-02-02 1:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 6:49 [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues Hangbin Liu
2026-01-14 6:49 ` [PATCHv2 net-next 1/3] bonding: set AD_RX_PORT_DISABLED when disabling a port Hangbin Liu
2026-01-14 6:49 ` [PATCHv2 net-next 2/3] bonding: restructure ad_churn_machine Hangbin Liu
2026-01-19 20:22 ` Jakub Kicinski
2026-01-20 5:51 ` Hangbin Liu
2026-01-20 8:29 ` Paolo Abeni
2026-01-20 23:11 ` Jakub Kicinski
2026-01-21 7:58 ` Paolo Abeni
2026-01-22 1:10 ` Jakub Kicinski
2026-01-14 6:49 ` [PATCHv2 net-next 3/3] selftests: bonding: add mux and churn state testing Hangbin Liu
2026-02-02 1:14 ` Hangbin Liu [this message]
2026-02-02 9:27 ` [PATCHv2 net-next 0/3] bonding: fix 802.3ad churn machine and port state issues Paolo Abeni
2026-02-23 1:55 ` Hangbin Liu
2026-02-26 11:55 ` Paolo Abeni
2026-02-26 12:40 ` Hangbin Liu
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=aX_6jyAQaDoqsR3G@fedora \
--to=liuhangbin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.