From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Antonio Quartulli <antonio@mandelbit.com>,
willemdebruijn.kernel@gmail.com, jasowangio@gmail.com
Cc: Antonio Quartulli <antonio@mandelbit.com>,
andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, mst@redhat.com, eperezma@redhat.com,
shuah@kernel.org, ast@kernel.org, daniel@iogearbox.net,
hawk@kernel.org, john.fastabend@gmail.com, sdf@fomichev.me,
maheshb@google.com, peterpenkov96@gmail.com,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net v5 1/2] tun: bound the NAPI receive queue
Date: Thu, 12 Nov 2026 18:28:20 -0500 [thread overview]
Message-ID: <willemdebruijn.kernel.1122b304c2dc4@gmail.com> (raw)
In-Reply-To: <20261111014208.1795777-2-antonio@mandelbit.com>
Antonio Quartulli wrote:
> With IFF_NAPI, tun_get_user() queues every written packet for NAPI on
> an unbounded list. When the poll runs asynchronously (threaded NAPI)
> and is slower than the writer, the queue grows until the system runs
> out of memory. An unprivileged user can do this from its own user and
> network namespaces, and the queued skbs are not charged to its memcg:
> in a test VM, a uid 1000 process limited to 128 MB caused a global OOM
> in ~6 seconds. The socket send buffer cannot bound this: tun sets it to
> INT_MAX, and the build_skb() and XDP batch paths do not check it.
>
> Drop packets once more than netdev_max_backlog of them are queued, like
> enqueue_to_backlog() does, and count them as rx_dropped, before
> allocating and copying them. This covers write(), sendmsg() and the
> batches of XDP buffers vhost-net passes to tun_sendmsg(), which share
> the queue. Zerocopy buffers of dropped packets are completed. The check
> is lockless, so concurrent writers can each still add one packet.
>
> The NAPI poll moved the whole queue out, processed up to its budget and
> put the rest back: while it ran, the queue looked empty to writers, so
> with the poll on another CPU the backlog could still grow without limit.
> Take at most budget packets instead, so that the queue never looks
> emptier than it is.
>
> Dropping because the queue is full also schedules NAPI. vhost-net sends
> with MSG_MORE while it has more packets, and tun_get_user() schedules
> NAPI only after the last one or once more than NAPI_POLL_WEIGHT are
> queued. With a netdev_max_backlog below that, the queue would not drain
> until vhost-net ran out of packets; with zerocopy, vhost-net never
> would, as it stops sending when too many queued buffers are pending.
>
> Reproducer, as an unprivileged user in a new user and network
> namespace, without kernel modifications or fault injection:
> ip tuntap add t0 mode tun; ip addr add 10.11.0.1/24 dev t0
> ip link add d0 type dummy; ip addr add 10.20.0.1/24 dev d0
> ip link set t0 up; ip link set d0 up; sysctl net.ipv4.ip_forward=1
> install ~500 iptables FORWARD rules and a MASQUERADE rule on d0
> open t0 with IFF_TUN | IFF_NO_PI | IFF_NAPI
> echo 1 > /sys/class/net/t0/threaded
> write() 1400-byte IPv4 packets for 10.20.0.2 in a loop
>
> Tested in an x86-64 VM with 1 and 2 vCPUs: with the reproducer running
> for 15 seconds, with 1400 to 65000-byte packets, memory use stays flat
> and the forwarding rate is unchanged; the tun kselftest passes, as it
> does without the patch; and the tun_vhost kselftest added by the next
> patch, which drives the vhost-net batch, copy and zerocopy paths,
> passes, while it fails without the patch.
>
> Still open: the limit counts packets rather than bytes and applies per
> queue, so with large packets and many queues (IFF_MULTI_QUEUE works in a
> user namespace too) the queued skbs, which are not charged to the
> writer's memcg, can still add up to an OOM. This is hard to reach in
> practice: with large packets the writer's copy is slower than the NAPI
> poll, so the queue does not fill. With 64 KB writes the reproducer never
> reached the limit and memory use stayed flat.
>
> Found while analysing the performance of the tun write path, and tested,
> with the help of an AI coding assistant (Claude Code).
>
> Fixes: 943170998b20 ("tun: enable NAPI for TUN/TAP driver")
> Signed-off-by: Antonio Quartulli <antonio@mandelbit.com>
> ---
> drivers/net/tun.c | 59 ++++++++++++++++++++++++++++++++++++++++-------
> 1 file changed, 51 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/tun.c b/drivers/net/tun.c
> index dcec7311e601..396e4295589f 100644
> --- a/drivers/net/tun.c
> +++ b/drivers/net/tun.c
> @@ -58,6 +58,7 @@
> #include <linux/nsproxy.h>
> #include <linux/virtio_net.h>
> #include <linux/rcupdate.h>
> +#include <net/hotdata.h>
> #include <net/net_namespace.h>
> #include <net/netns/generic.h>
> #include <net/rtnetlink.h>
> @@ -227,6 +228,16 @@ struct veth {
> static void tun_flow_init(struct tun_struct *tun);
> static void tun_flow_uninit(struct tun_struct *tun);
>
> +/* In IFF_NAPI mode written packets wait in the tfile's sk_write_queue for the
> + * NAPI poll, which may run later in a kthread or ksoftirqd. Bound that queue
> + * like the per-CPU backlog of netif_rx().
> + */
> +static bool tun_napi_queue_full(const struct sk_buff_head *queue)
> +{
> + return skb_queue_len_lockless(queue) >
> + READ_ONCE(net_hotdata.max_backlog);
> +}
> +
> static int tun_napi_receive(struct napi_struct *napi, int budget)
> {
> struct tun_file *tfile = container_of(napi, struct tun_file, napi);
> @@ -237,21 +248,24 @@ static int tun_napi_receive(struct napi_struct *napi, int budget)
>
> __skb_queue_head_init(&process_queue);
>
> + /* Take at most budget skbs, so that the queue never looks emptier to
> + * writers than it is.
> + */
> spin_lock(&queue->lock);
> - skb_queue_splice_tail_init(queue, &process_queue);
> + if (skb_queue_len(queue) <= budget) {
> + skb_queue_splice_tail_init(queue, &process_queue);
> + } else {
> + while (skb_queue_len(&process_queue) < budget &&
> + (skb = __skb_dequeue(queue)))
> + __skb_queue_tail(&process_queue, skb);
> + }
> spin_unlock(&queue->lock);
>
> - while (received < budget && (skb = __skb_dequeue(&process_queue))) {
> + while ((skb = __skb_dequeue(&process_queue))) {
> napi_gro_receive(napi, skb);
> ++received;
> }
>
> - if (!skb_queue_empty(&process_queue)) {
> - spin_lock(&queue->lock);
> - skb_queue_splice(&process_queue, queue);
> - spin_unlock(&queue->lock);
> - }
> -
> return received;
> }
>
> @@ -1856,6 +1870,24 @@ static ssize_t tun_get_user(struct tun_struct *tun, struct tun_file *tfile,
> zerocopy = true;
> }
>
> + /* NAPI queue full: drop before allocating, and schedule NAPI, which a
> + * MSG_MORE sender may not have done yet. Lockless: concurrent writers
> + * can each still add one.
> + */
> + if (tfile->napi_enabled &&
> + unlikely(tun_napi_queue_full(&tfile->sk.sk_write_queue))) {
> + local_bh_disable();
> + napi_schedule(&tfile->napi);
> + local_bh_enable();
> + if (msg_control) {
> + struct ubuf_info *uarg = msg_control;
> +
> + uarg->ops->complete(NULL, uarg, false);
call net_zcopy_put
even if the packet is dropped, the entire operation was without
fall-back to copying, so last argument is true.
also stops vhost-net from falling back onto copy mode
> + }
> + dev_core_stats_rx_dropped_inc(tun->dev);
> + return total_len;
> + }
> +
> if (!frags && tun_can_build_skb(tun, tfile, len, noblock, zerocopy)) {
> /* For the packet that is not easy to be processed
> * (e.g gso or jumbo packet), we will do it at after
> @@ -2561,6 +2593,17 @@ static int tun_xdp_one(struct tun_struct *tun,
> return -EIO;
> }
>
> + /* NAPI queue full: drop, and schedule NAPI so that it drains even if
> + * nothing in this batch gets queued
> + */
> + if (tfile->napi_enabled &&
> + unlikely(tun_napi_queue_full(&tfile->sk.sk_write_queue))) {
> + napi_schedule(&tfile->napi);
> + put_page(virt_to_head_page(xdp->data));
> + dev_core_stats_rx_dropped_inc(tun->dev);
> + return 0;
> + }
> +
> xdp_prog = rcu_dereference(tun->xdp_prog);
> if (xdp_prog) {
> if (gso->gso_type) {
> --
> 2.56.0
>
next prev parent reply other threads:[~2026-11-12 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 1:42 [PATCH net v5 0/2] tun: bound the NAPI receive queue Antonio Quartulli
2026-11-11 1:42 ` [PATCH net v5 1/2] " Antonio Quartulli
2026-11-12 23:28 ` Willem de Bruijn [this message]
2026-11-13 0:29 ` Antonio Quartulli
2026-11-11 1:42 ` [PATCH net v5 2/2] selftests: net: add a vhost-net test for the tun NAPI queue bound Antonio Quartulli
2026-11-12 23:34 ` Willem de Bruijn
2026-11-13 0:33 ` Antonio Quartulli
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=willemdebruijn.kernel.1122b304c2dc4@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=antonio@mandelbit.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=eperezma@redhat.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=jasowangio@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maheshb@google.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peterpenkov96@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
/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.