Re: [PATCH net v2] vxlan: vnifilter: validate the VNI range in vni_filter_entry_policy

From
Ido Schimmel <idosch@nvidia.com>
Date
2026-09-07 14:10:21
Reply to
Ali Firas, 2026-09-07
On Mon, Sep 07, 2026 at 01:52:23PM +0300, Ali Firas wrote:
So I have the accounting patch ready, but I would rather not send it as
if it closed the problem when it closes half of it. Would you prefer the
accounting patch on its own with the rtnl stall described as a known
remaining issue, or is the stall something you would want addressed
first, in which case I would need guidance on whether a cap is
acceptable at all?
Limiting the VNI range to 4k at a time is unlikely to break anyone given
that "vnifilter" is mainly used on bridged VXLAN devices where the VNI
is derived from the VLAN (max 4094).

There are no selftests for the range functionality, so as part of this
work please add some in test_vxlan_vnifiltering.sh. At the very least we
should make sure that the max range is accepted and 'max + 1' is
rejected (for both add and delete).
Thread (15 messages) 15 messages, 4 authors, last reply 2026-09-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help