From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
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>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] bonding: report duplicate MAC address in all situations
Date: Tue, 25 Feb 2025 03:10:40 +0000 [thread overview]
Message-ID: <Z700sKO3sBkxf8Ra@fedora> (raw)
In-Reply-To: <20250224141008.3ee3a74b@kernel.org>
Hi Jakub,
On Mon, Feb 24, 2025 at 02:10:08PM -0800, Jakub Kicinski wrote:
> On Wed, 19 Feb 2025 07:55:15 +0000 Hangbin Liu wrote:
> > Normally, a bond uses the MAC address of the first added slave as the
> > bond’s MAC address. And the bond will set active slave’s MAC address to
> > bond’s address if fail_over_mac is set to none (0) or follow (2).
> >
> > When the first slave is removed, the bond will still use the removed
> > slave’s MAC address, which can lead to a duplicate MAC address and
> > potentially cause issues with the switch. To avoid confusion, let's warn
> > the user in all situations, including when fail_over_mac is set to 2 or
> > in active-backup mode.
>
> Makes sense, thanks for the high quality commit message.
>
> False positive warnings are annoying to users (especially users who
> monitor all warnings in their fleet). Could we stick to filtering out
> the BOND_FOM_ACTIVE case? Looks like this condition:
>
> if (bond->params.fail_over_mac != BOND_FOM_ACTIVE ||
> BOND_MODE(bond) != BOND_MODE_ACTIVEBACKUP) {
>
> exists a few lines later in __bond_release_one()
You are right. The bond will change the mac address later if
bond mode is active_backup and fail_over_mac is active
if (oldcurrent == slave)
bond_change_active_slave(bond, NULL);
With the upper mode and parameter, during the slave_warn(), bond is still
using the same mac addr with the first join and released slave's mac address
and cause false positive warn.
I will update the if condition. Thanks for your review.
Regards
Hangbin
>
> > diff --git a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
> > index e45bba240cbc..ca66107776cc 100644
> > --- a/drivers/net/bonding/bond_main.c
> > +++ b/drivers/net/bonding/bond_main.c
> > @@ -2551,13 +2551,11 @@ static int __bond_release_one(struct net_device *bond_dev,
> >
> > RCU_INIT_POINTER(bond->current_arp_slave, NULL);
> >
> > - if (!all && (!bond->params.fail_over_mac ||
> > - BOND_MODE(bond) != BOND_MODE_ACTIVEBACKUP)) {
> > - if (ether_addr_equal_64bits(bond_dev->dev_addr, slave->perm_hwaddr) &&
> > - bond_has_slaves(bond))
> > - slave_warn(bond_dev, slave_dev, "the permanent HWaddr of slave - %pM - is still in use by bond - set the HWaddr of slave to a different address to avoid conflicts\n",
> > - slave->perm_hwaddr);
> > - }
> > + if (!all &&
> > + ether_addr_equal_64bits(bond_dev->dev_addr, slave->perm_hwaddr) &&
> > + bond_has_slaves(bond))
> > + slave_warn(bond_dev, slave_dev, "the permanent HWaddr of slave - %pM - is still in use by bond - set the HWaddr of slave to a different address to avoid conflicts\n",
> > + slave->perm_hwaddr);
> --
> pw-bot: cr
prev parent reply other threads:[~2025-02-25 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 7:55 [PATCH net-next] bonding: report duplicate MAC address in all situations Hangbin Liu
2025-02-24 22:10 ` Jakub Kicinski
2025-02-25 3:10 ` Hangbin Liu [this message]
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=Z700sKO3sBkxf8Ra@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-kernel@vger.kernel.org \
--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).