All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, vtlam@google.com, stable@vger.kernel.org,
	victor@mojatatu.com, hybris@mojatatu.ai, sashiko-bot@kernel.org
Subject: Re: [PATCH net 1/2] net/sched: hhf: cap hh_flows_limit at change time
Date: Tue, 15 Sep 2026 13:00:04 +0000	[thread overview]
Message-ID: <178947720466.1607766.7479529593447485027.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <QDISC-B855.v1.20260911153152@mojatatu.com>

Hello:

This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Sat, 12 Sep 2026 14:09:19 -0400 you wrote:
> hhf_change() stores TCA_HHF_HH_FLOWS_LIMIT with no upper bound. A huge
> hh_flows_limit lets each new heavy-hitter flow pass the
> hh_flows_current_cnt check in alloc_new_hh() and forces a fixed-size
> kzalloc(GFP_ATOMIC) per flow under spoofed traffic, for unbounded memory
> growth.
> 
> Bound the attribute with NLA_POLICY_MAX() at 2*HH_FLOWS_CNT (the
> hhf_init() default) and report the rejected value via extack. The
> deprecated nested parse is kept: legacy tc does not set NLA_F_NESTED on
> TCA_OPTIONS. Configs relying on hh_limit above the default were relying
> on unbounded, unsafe behaviour and are not supported going forward.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net/sched: hhf: cap hh_flows_limit at change time
    https://git.kernel.org/netdev/net/c/2cef2588c995
  - [net,2/2] selftests/tc-testing: add hhf hh_limit cap tests
    https://git.kernel.org/netdev/net/c/0654f4dba1fb

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-15 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-12 18:09 [PATCH net 1/2] net/sched: hhf: cap hh_flows_limit at change time Jamal Hadi Salim
2026-09-12 18:09 ` [PATCH net 2/2] selftests/tc-testing: add hhf hh_limit cap tests Jamal Hadi Salim
2026-09-12 20:36   ` netdev-bot+sashiko
2026-09-14  9:14   ` Simon Horman
2026-09-12 20:36 ` [PATCH net 1/2] net/sched: hhf: cap hh_flows_limit at change time netdev-bot+sashiko
2026-09-13 10:34   ` Jamal Hadi Salim
2026-09-14  9:14     ` Simon Horman
2026-09-15 13:00 ` 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=178947720466.1607766.7479529593447485027.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=stable@vger.kernel.org \
    --cc=victor@mojatatu.com \
    --cc=vtlam@google.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.