netdev - Re: [PATCHv3 net] bonding: assign random address if device address is same as bond

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <174584042976.546496.2585369633410205037.git-patchwork-notify@kernel.org>
Date: Mon, 28 Apr 2025 11:40:29 +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, cratiu@...dia.com,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCHv3 net] bonding: assign random address if device address is
 same as bond

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.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