From: Jakub Kicinski <kuba@kernel.org>
To: Ali Firas <alishmery18@gmail.com>
Cc: netdev@vger.kernel.org, idosch@nvidia.com, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com, andrew+netdev@lunn.ch,
razor@blackwall.org, roopa@nvidia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/3] vxlan: vnifilter: limit the VNI range of a single request
Date: Mon, 14 Sep 2026 17:31:03 -0700 [thread overview]
Message-ID: <20260914173103.539d8838@kernel.org> (raw)
In-Reply-To: <20260909092645.3105263-2-alishmery18@gmail.com>
On Wed, 9 Sep 2026 12:26:43 +0300 Ali Firas wrote:
> VXLAN_VNIFILTER_ENTRY_START and VXLAN_VNIFILTER_ENTRY_END are parsed
> without any bound on how far apart they are, so a single RTM_NEWTUNNEL
> message can ask for the whole 24-bit VNI space. vxlan_vni_add_del() then
> loops over that span creating one VNI node and one per-CPU stats block
> per iteration, all under rtnl_lock.
The AI review looks legit.
Please target net-next without a fixes tag for this.
Please do _not_ send the next version in reply to a previous posting.
next prev parent reply other threads:[~2026-09-15 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 15:46 [PATCH net v2] vxlan: vnifilter: validate the VNI range in vni_filter_entry_policy Ali Firas
2026-09-05 19:36 ` netdev-bot+sashiko
2026-09-05 19:39 ` Jakub Kicinski
2026-09-06 23:16 ` Ali Firas
2026-09-07 10:52 ` Ali Firas
2026-09-07 14:10 ` Ido Schimmel
2026-09-09 9:26 ` [PATCH net 0/3] vxlan: vnifilter: bound the VNI range per request Ali Firas
2026-09-09 9:26 ` [PATCH net 1/3] vxlan: vnifilter: limit the VNI range of a single request Ali Firas
2026-09-10 9:38 ` netdev-bot+sashiko
2026-09-15 0:31 ` Jakub Kicinski [this message]
2026-09-09 9:26 ` [PATCH net 2/3] vxlan: vnifilter: account VNI node and per-CPU stats to memcg Ali Firas
2026-09-10 9:38 ` netdev-bot+sashiko
2026-09-15 0:31 ` Jakub Kicinski
2026-09-09 9:26 ` [PATCH net 3/3] selftests: net: test the vxlan vnifilter VNI range limit Ali Firas
2026-09-10 9:39 ` netdev-bot+sashiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260914173103.539d8838@kernel.org \
--to=kuba@kernel.org \
--cc=alishmery18@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=roopa@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.