All of lore.kernel.org
 help / color / mirror / Atom feed
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@kernel.org, andrew+netdev@lunn.ch,
	horms@kernel.org, razor@blackwall.org, roopa@nvidia.com,
	kuniyu@google.com, petrm@nvidia.com, aroulin@nvidia.com,
	shuah@kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/8] vxlan: vnifilter: bound a single request and account per-VNI memory
Date: Fri, 20 Nov 2026 16:26:20 -0800	[thread overview]
Message-ID: <20261120162620.0b018d12@kernel.org> (raw)
In-Reply-To: <20261114221412.255825-1-alishmery18@gmail.com>

On Sun, 15 Nov 2026 01:14:04 +0300 Ali Firas 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.

I will take patches 1 and 4, those are trivial. The rest of it - 
not sure, nobody seems to think this is worth reviewing..

  parent reply	other threads:[~2026-11-21  0:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-14 22:14 [PATCH net-next v5 0/8] vxlan: vnifilter: bound a single request and account per-VNI memory Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 1/8] vxlan: vnifilter: reject VNIs outside the 24-bit space Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 2/8] vxlan: vnifilter: clamp the dumped VNI range to the request limit Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 3/8] vxlan: vnifilter: bound the number of VNIs one request may touch Ali Firas
2026-11-16  5:32   ` netdev-bot+sashiko
2026-11-14 22:14 ` [PATCH net-next v5 4/8] vxlan: vnifilter: account per-VNI memory to memcg Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 5/8] vxlan: leave FDB state and flags unchanged when an update fails Ali Firas
2026-11-16  5:32   ` netdev-bot+sashiko
2026-11-14 22:14 ` [PATCH net-next v5 6/8] vxlan: vnifilter: roll back a VNI add that fails Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 7/8] vxlan: vnifilter: account the default FDB entry to memcg Ali Firas
2026-11-14 22:14 ` [PATCH net-next v5 8/8] selftests: net: test the vxlan vnifilter request limit and dump replay Ali Firas
2026-11-16  5:32   ` netdev-bot+sashiko
2026-11-21  0:26 ` Jakub Kicinski [this message]
2026-11-21  0:30 ` [PATCH net-next v5 0/8] vxlan: vnifilter: bound a single request and account per-VNI memory patchwork-bot+netdevbpf

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=20261120162620.0b018d12@kernel.org \
    --to=kuba@kernel.org \
    --cc=alishmery18@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=aroulin@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    --cc=shuah@kernel.org \
    /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.