From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
stable@vger.kernel.org, vega@nebusec.ai,
Victor Nogueira <victor@mojatatu.com>
Subject: Re: [PATCH net v2] net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup
Date: Mon, 24 Aug 2026 11:36:27 -0700 [thread overview]
Message-ID: <20260824113627.201f795f@kernel.org> (raw)
In-Reply-To: <CAM0EoMmhjJyBZArFUdVBzzw6Ko6C9thDgOL-VMU1jDTAhS_qYA@mail.gmail.com>
On Wed, 19 Aug 2026 11:30:44 -0400 Jamal Hadi Salim wrote:
> I see. I was looking for something reasonable. The problem is maximum
> real skb->len is UINT_MAX and with stab amplification it can get a
> small packet into a GB.
> Would you prefer a new #define in pkt_sched.h to put an upper bound
> (QDISC_PKT_LEN_MAX)?
> Something else?
Let's go with the define you mentioned to make progress.
--
pw-bot: cr
next prev parent reply other threads:[~2026-08-24 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 14:32 [PATCH net v2] net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup Jamal Hadi Salim
2026-08-19 14:52 ` Eric Dumazet
2026-08-19 14:58 ` Jamal Hadi Salim
2026-08-19 15:15 ` Eric Dumazet
2026-08-19 15:30 ` Jamal Hadi Salim
2026-08-24 18:36 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-25 8:14 Jamal Hadi Salim
2026-08-27 11:01 ` Paolo Abeni
2026-08-27 17:48 ` Jamal Hadi Salim
2026-08-27 19:40 ` 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=20260824113627.201f795f@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox