Re: [PATCH net-next v4 0/7] vxlan: vnifilter: bound a single request and account per-VNI memory

[patchwork-bot+netdevbpf]

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@xxxxxxxxxx>:

On Wed, 14 Oct 2026 15:38:07 +0300 you wrote:
> The VNI filter interface accepts a START/END range with no bound on
> either endpoint and no bound on how many VNIs one message may ask for,
> and the memory it allocates per VNI is not charged to the caller's
> cgroup.
> 
> Patch 1 links the VXLAN_VNIFILTER_ENTRY nest to its policy with
> NLA_POLICY_NESTED(), as Jakub asked in v2:
> 
> [...]

Here is the summary with links:
  - [net-next,v4,1/7] vxlan: vnifilter: validate the VXLAN_VNIFILTER_ENTRY nest
    https://git.kernel.org/netdev/net-next/c/599d0e97610f
  - [net-next,v4,2/7] vxlan: vnifilter: reject VNIs outside the 24-bit space
    (no matching commit)
  - [net-next,v4,3/7] vxlan: vnifilter: clamp the dumped VNI range to the request limit
    (no matching commit)
  - [net-next,v4,4/7] vxlan: vnifilter: bound the number of VNIs one request may touch
    (no matching commit)
  - [net-next,v4,5/7] vxlan: vnifilter: account per-VNI memory to memcg
    (no matching commit)
  - [net-next,v4,6/7] vxlan: vnifilter: account the default FDB entry to memcg
    (no matching commit)
  - [net-next,v4,7/7] 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