| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id:
<174062883599.960972.8510053469556402775.git-patchwork-notify@kernel.org>
Date: Thu, 27 Feb 2025 04:00:35 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Hangbin Liu <liuhangbin@...il.com>
Cc: netdev@...r.kernel.org, jv@...sburgh.net, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
razor@...ckwall.org, horms@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 net-next] bonding: report duplicate MAC address in all
situations
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 25 Feb 2025 03:39:14 +0000 you 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 not in active-backup
> mode.
>
> [...]
Here is the summary with links:
- [PATCHv2,net-next] bonding: report duplicate MAC address in all situations
https://git.kernel.org/netdev/net-next/c/28d68d396a1c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists