From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <jv@jvosburgh.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Nikolay Aleksandrov <razor@blackwall.org>,
Simon Horman <horms@kernel.org>, Cosmin Ratiu <cratiu@nvidia.com>,
linux-kernel@vger.kernel.org, Liang Li <liali@redhat.com>
Subject: Re: [PATCH net] bonding: use permanent address for MAC swapping if device address is same
Date: Tue, 25 Mar 2025 06:24:16 -0700 [thread overview]
Message-ID: <20250325062416.4d60681b@kernel.org> (raw)
In-Reply-To: <20250319080947.2001-1-liuhangbin@gmail.com>
On Wed, 19 Mar 2025 08:09:47 +0000 Hangbin Liu wrote:
> Similar with a951bc1e6ba5 ("bonding: correct the MAC address for "follow"
> fail_over_mac policy"). The fail_over_mac follow mode requires the formerly
> active slave to swap MAC addresses with the newly active slave during
> failover. However, the slave's MAC address can be same under certain
> conditions:
>
> 1) ip link set eth0 master bond0
> bond0 adopts eth0's MAC address (MAC0).
>
> 1) ip link set eth1 master bond0
nit: 2)
> eth1 is added as a backup with its own MAC (MAC1).
>
> 3) ip link set eth0 nomaster
> eth0 is released and restores its MAC (MAC0).
> eth1 becomes the active slave, and bond0 assigns MAC0 to eth1.
I don't know much about bonding, but this seems like a problem already
to me. Assuming both eth0 and eth1 are on the same segment we now have
two interfaces with the same MAC on the network. Shouldn't we override
the address of eth0 to a random one when it leaves?
> 4) ip link set eth0 master bond0
> eth0 is re-added to bond0, but both eth0 and eth1 now have MAC0,
> breaking the follow policy.
>
> To resolve this issue, we need to swap the new active slave’s permanent
> MAC address with the old one. The new active slave then uses the old
> dev_addr, ensuring that it matches the bond address. After the fix:
>
> 5) ip link set bond0 type bond active_slave eth0
> dev_addr is the same, swap old active eth1's MAC (MAC0) with eth0.
> Swap new active eth0's permanent MAC (MAC0) to eth1.
> MAC addresses remain unchanged.
>
> 6) ip link set bond0 type bond active_slave eth1
> dev_addr is the same, swap the old active eth0's MAC (MAC0) with eth1.
> Swap new active eth1's permanent MAC (MAC1) to eth0.
> The MAC addresses are now correctly differentiated.
>
> Fixes: 3915c1e8634a ("bonding: Add "follow" option to fail_over_mac")
> Reported-by: Liang Li <liali@redhat.com>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
> ---
> drivers/net/bonding/bond_main.c | 9 +++++++--
> include/net/bonding.h | 8 ++++++++
> 2 files changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> index e45bba240cbc..9cc2348d4ee9 100644
> --- a/drivers/net/bonding/bond_main.c
> +++ b/drivers/net/bonding/bond_main.c
> @@ -1107,8 +1107,13 @@ static void bond_do_fail_over_mac(struct bonding *bond,
> old_active = bond_get_old_active(bond, new_active);
>
> if (old_active) {
> - bond_hw_addr_copy(tmp_mac, new_active->dev->dev_addr,
> - new_active->dev->addr_len);
> + if (bond_hw_addr_equal(old_active->dev->dev_addr, new_active->dev->dev_addr,
> + new_active->dev->addr_len))
> + bond_hw_addr_copy(tmp_mac, new_active->perm_hwaddr,
> + new_active->dev->addr_len);
> + else
> + bond_hw_addr_copy(tmp_mac, new_active->dev->dev_addr,
> + new_active->dev->addr_len);
> bond_hw_addr_copy(ss.__data,
> old_active->dev->dev_addr,
> old_active->dev->addr_len);
> diff --git a/include/net/bonding.h b/include/net/bonding.h
> index 8bb5f016969f..de965c24dde0 100644
> --- a/include/net/bonding.h
> +++ b/include/net/bonding.h
> @@ -463,6 +463,14 @@ static inline void bond_hw_addr_copy(u8 *dst, const u8 *src, unsigned int len)
> memcpy(dst, src, len);
> }
>
> +static inline bool bond_hw_addr_equal(const u8 *dst, const u8 *src, unsigned int len)
> +{
> + if (len == ETH_ALEN)
> + return ether_addr_equal(dst, src);
> + else
> + return (memcmp(dst, src, len) == 0);
looks like this is on ctrl path, just always use memcmp directly ?
not sure if this helper actually.. helps.
> +}
> +
> #define BOND_PRI_RESELECT_ALWAYS 0
> #define BOND_PRI_RESELECT_BETTER 1
> #define BOND_PRI_RESELECT_FAILURE 2
--
pw-bot: cr
next prev parent reply other threads:[~2025-03-25 13:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 8:09 [PATCH net] bonding: use permanent address for MAC swapping if device address is same Hangbin Liu
2025-03-20 19:13 ` Jay Vosburgh
2025-03-24 2:30 ` Hangbin Liu
2025-03-25 13:24 ` Jakub Kicinski [this message]
2025-03-26 10:22 ` Hangbin Liu
2025-03-26 11:32 ` Jakub Kicinski
2025-03-26 14:18 ` Hangbin Liu
2025-04-03 14:02 ` Paolo Abeni
2025-04-07 7:57 ` 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=20250325062416.4d60681b@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=liali@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).