From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, jv@jvosburgh.net, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, razor@blackwall.org, horms@kernel.org,
cratiu@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 net] bonding: assign random address if device address is same as bond
Date: Mon, 28 Apr 2025 11:40:29 +0000 [thread overview]
Message-ID: <174584042976.546496.2585369633410205037.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250424042238.618289-1-liuhangbin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 24 Apr 2025 04:22:38 +0000 you wrote:
> This change addresses a MAC address conflict issue in failover scenarios,
> similar to the problem described in commit a951bc1e6ba5 ("bonding: correct
> the MAC address for 'follow' fail_over_mac policy").
>
> In fail_over_mac=follow mode, the bonding driver expects the formerly active
> slave to swap MAC addresses with the newly active slave during failover.
> However, under certain conditions, two slaves may end up with the same MAC
> address, which breaks this policy:
>
> [...]
Here is the summary with links:
- [PATCHv3,net] bonding: assign random address if device address is same as bond
https://git.kernel.org/netdev/net-next/c/5c3bf6cba791
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-04-28 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 4:22 [PATCHv3 net] bonding: assign random address if device address is same as bond Hangbin Liu
2025-04-24 23:44 ` Jay Vosburgh
2025-04-26 2:04 ` Jakub Kicinski
2025-04-26 3:51 ` Jay Vosburgh
2025-04-28 11:40 ` patchwork-bot+netdevbpf [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=174584042976.546496.2585369633410205037.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@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=kuba@kernel.org \
--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).