From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, donald.hunter@gmail.com,
vega@nebusec.ai, victor@mojatatu.com
Subject: Re: [PATCH net v2 0/3] net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations
Date: Fri, 04 Sep 2026 23:40:10 +0000 [thread overview]
Message-ID: <178856521039.1019727.11940822267177362056.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-2899.v2.20260901233641@mojatatu.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Sep 2026 17:29:07 -0400 you wrote:
> An unprivileged user (via unshare -Urn) can set a huge tx_queue_len
> and exhaust global memory through ring allocations sized from it
> (pfifo_fast skb_arrays, tun/tap ptr_rings).
> The reproducer from vega@nebusec.ai set the following params for
> illustration: txqlen of 500000 -> ~32 GiB/ring attempts, 1.6 GB tun,
> ~960 MB tap. Gets worse when you consider qdiscs like mq.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations
https://git.kernel.org/netdev/net/c/66ab4c59b74d
- [net,v2,2/3] net: reject oversized tx_queue_len at netlink parse time
https://git.kernel.org/netdev/net/c/1aa9e143bf51
- [net,v2,3/3] selftests: tc-testing: add tx_queue_len cap regression tests
https://git.kernel.org/netdev/net/c/0a7252d7f854
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-09-04 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 21:29 [PATCH net v2 0/3] net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations Jamal Hadi Salim
2026-09-02 21:29 ` Jamal Hadi Salim
2026-09-02 21:29 ` [PATCH net v2 1/3] " Jamal Hadi Salim
2026-09-02 21:29 ` [PATCH net v2 2/3] net: reject oversized tx_queue_len at netlink parse time Jamal Hadi Salim
2026-09-05 1:10 ` netdev-bot+sashiko
2026-09-02 21:29 ` [PATCH net v2 3/3] selftests: tc-testing: add tx_queue_len cap regression tests Jamal Hadi Salim
2026-09-05 1:10 ` netdev-bot+sashiko
2026-09-04 23:40 ` patchwork-bot+netdevbpf [this message]
2026-09-05 1:10 ` [PATCH net v2 1/3] net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations 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=178856521039.1019727.11940822267177362056.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=vega@nebusec.ai \
--cc=victor@mojatatu.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.