Re: [PATCH net-next v5 0/8] vxlan: vnifilter: bound a single request and account per-VNI memory
From: patchwork-bot+netdevbpf
Date: Fri Nov 20 2026 - 19:30:13 EST
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:
On Sun, 15 Nov 2026 01:14:04 +0300 you wrote:
> The VNI filter interface accepts a VNI range with no bound on either
> endpoint or on how many VNIs one message may ask for, and the memory it
> allocates per VNI is not charged to the caller's cgroup. Charging it
> makes adding a VNI, or changing its remote, fail routinely at a cgroup
> limit, which exposes two error paths that leave configuration state
> inconsistent; patches 5 and 6 fix those first.
>
> [...]
Here is the summary with links:
- [net-next,v5,1/8] vxlan: vnifilter: reject VNIs outside the 24-bit space
https://git.kernel.org/netdev/net-next/c/4d00df6019f8
- [net-next,v5,2/8] vxlan: vnifilter: clamp the dumped VNI range to the request limit
(no matching commit)
- [net-next,v5,3/8] vxlan: vnifilter: bound the number of VNIs one request may touch
(no matching commit)
- [net-next,v5,4/8] vxlan: vnifilter: account per-VNI memory to memcg
https://git.kernel.org/netdev/net-next/c/39508fb293a9
- [net-next,v5,5/8] vxlan: leave FDB state and flags unchanged when an update fails
(no matching commit)
- [net-next,v5,6/8] vxlan: vnifilter: roll back a VNI add that fails
(no matching commit)
- [net-next,v5,7/8] vxlan: vnifilter: account the default FDB entry to memcg
(no matching commit)
- [net-next,v5,8/8] selftests: net: test the vxlan vnifilter request limit and dump replay
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html