From: patchwork-bot+netdevbpf@kernel.org
To: Victor Nogueira <victor@mojatatu.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jhs@mojatatu.com, jiri@resnulli.us,
netdev@vger.kernel.org, horms@kernel.org, hybris@mojatatu.ai,
sashiko-bot@kernel.org
Subject: Re: [PATCH net] net/sched: act_gate: budget the per-entry list in get_fill_size
Date: Wed, 23 Sep 2026 23:50:06 +0000 [thread overview]
Message-ID: <179020740618.999807.15161561763499463273.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-3BLH.v1.20260914203033@mojatatu.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 20 Sep 2026 14:07:01 -0300 you wrote:
> tcf_gate_get_fill_size returns only the TCA_GATE_PARMS size, but
> tcf_gate_dump also emits three 64-bit timestamps, the clock id, flags,
> priority and the variable-length TCA_GATE_ENTRY_LIST nest. The per-entry
> nest is unbounded: parse_gate_list places no cap on the number of
> sched-entries, so a gate with many entries can push the real dump well
> past the skb that tca_get_fill allocates from this size.
>
> [...]
Here is the summary with links:
- [net] net/sched: act_gate: budget the per-entry list in get_fill_size
https://git.kernel.org/netdev/net/c/cfa165cbfbed
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-23 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 17:07 [PATCH net] net/sched: act_gate: budget the per-entry list in get_fill_size Victor Nogueira
2026-09-23 23:50 ` patchwork-bot+netdevbpf [this message]
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=179020740618.999807.15161561763499463273.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hybris@mojatatu.ai \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--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