From: Jakub Kicinski <kuba@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: alishmery18@gmail.com, netdev@vger.kernel.org, idosch@nvidia.com,
pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
andrew+netdev@lunn.ch, horms@kernel.org, razor@blackwall.org,
roopa@nvidia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/5] vxlan: vnifilter: reject VNIs outside the 24-bit space
Date: Mon, 21 Sep 2026 15:09:04 -0700 [thread overview]
Message-ID: <20260921150904.65a704eb@kernel.org> (raw)
In-Reply-To: <178977729000.22033.11804607706102932436@kernel.org>
On Sat, 19 Sep 2026 00:21:30 +0000 netdev-bot+sashiko@kernel.org wrote:
> The top-level nlmsg_parse() in vxlan_vnifilter_process() uses
> vni_filter_policy, where the nest has no nested_policy pointer, and
> lib/nlattr.c only recurses when pt->nested_policy is set:
>
> static const struct nla_policy vni_filter_policy[VXLAN_VNIFILTER_MAX + 1] = {
> [VXLAN_VNIFILTER_ENTRY] = { .type = NLA_NESTED },
> };
Sounds legit, please link it with NLA_POLICY_NESTED() as patch 1
in the series
next prev parent reply other threads:[~2026-09-21 22:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 19:34 [PATCH net-next v2 0/5] vxlan: vnifilter: bound one request and account per-VNI memory Ali Firas
2026-09-16 19:34 ` [PATCH net-next v2 1/5] vxlan: vnifilter: reject VNIs outside the 24-bit space Ali Firas
2026-09-19 0:21 ` netdev-bot+sashiko
2026-09-21 22:09 ` Jakub Kicinski [this message]
2026-09-16 19:34 ` [PATCH net-next v2 2/5] vxlan: vnifilter: bound the number of VNIs one request may touch Ali Firas
2026-09-19 0:21 ` netdev-bot+sashiko
2026-09-16 19:34 ` [PATCH net-next v2 3/5] net: account per-CPU netdev stats to memcg Ali Firas
2026-09-19 0:21 ` netdev-bot+sashiko
2026-09-16 19:34 ` [PATCH net-next v2 4/5] vxlan: vnifilter: account the VNI node " Ali Firas
2026-09-19 0:21 ` netdev-bot+sashiko
2026-09-16 19:34 ` [PATCH net-next v2 5/5] selftests: net: test the vxlan vnifilter VNI limit Ali Firas
2026-09-19 0:21 ` 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=20260921150904.65a704eb@kernel.org \
--to=kuba@kernel.org \
--cc=alishmery18@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev-bot+sashiko@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.