[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175814761201.2168096.8321259039985302148.git-patchwork-notify@kernel.org>
Date: Wed, 17 Sep 2025 22:20:12 +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,
horms@...nel.org, shuah@...nel.org, linux-kselftest@...r.kernel.org,
wilder@...ibm.com
Subject: Re: [PATCHv4 net 1/2] bonding: don't set oif to bond dev when getting
NS
target destination
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 16 Sep 2025 08:01:26 +0000 you wrote:
> Unlike IPv4, IPv6 routing strictly requires the source address to be valid
> on the outgoing interface. If the NS target is set to a remote VLAN interface,
> and the source address is also configured on a VLAN over a bond interface,
> setting the oif to the bond device will fail to retrieve the correct
> destination route.
>
> Fix this by not setting the oif to the bond device when retrieving the NS
> target destination. This allows the correct destination device (the VLAN
> interface) to be determined, so that bond_verify_device_path can return the
> proper VLAN tags for sending NS messages.
>
> [...]
Here is the summary with links:
- [PATCHv4,net,1/2] bonding: don't set oif to bond dev when getting NS target destination
https://git.kernel.org/netdev/net/c/a8ba87f04ca9
- [PATCHv4,net,2/2] selftests: bonding: add vlan over bond testing
https://git.kernel.org/netdev/net/c/dc5f94b1ec8f
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