[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173119862775.3043730.8123158047350078052.git-patchwork-notify@kernel.org>
Date: Sun, 10 Nov 2024 00:30:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ido Schimmel <idosch@...dia.com>
Cc: netdev@...r.kernel.org, bridge@...ts.linux-foundation.org,
davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com, edumazet@...gle.com,
razor@...ckwall.org, roopa@...dia.com, horms@...nel.org, petrm@...dia.com,
aroulin@...dia.com
Subject: Re: [PATCH net-next] bridge: Allow deleting FDB entries with non-existent
VLAN
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 5 Nov 2024 15:39:54 +0200 you wrote:
> It is currently impossible to delete individual FDB entries (as opposed
> to flushing) that were added with a VLAN that no longer exists:
>
> # ip link add name dummy1 up type dummy
> # ip link add name br1 up type bridge vlan_filtering 1
> # ip link set dev dummy1 master br1
> # bridge fdb add 00:11:22:33:44:55 dev dummy1 master static vlan 1
> # bridge vlan del vid 1 dev dummy1
> # bridge fdb get 00:11:22:33:44:55 br br1 vlan 1
> 00:11:22:33:44:55 dev dummy1 vlan 1 master br1 static
> # bridge fdb del 00:11:22:33:44:55 dev dummy1 master vlan 1
> RTNETLINK answers: Invalid argument
> # bridge fdb get 00:11:22:33:44:55 br br1 vlan 1
> 00:11:22:33:44:55 dev dummy1 vlan 1 master br1 static
>
> [...]
Here is the summary with links:
- [net-next] bridge: Allow deleting FDB entries with non-existent VLAN
https://git.kernel.org/netdev/net-next/c/774ca6d3bf24
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