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,
horms@kernel.org, baowen.zheng@corigine.com,
louis.peens@corigine.com, pctammela@mojatatu.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net 0/4] net/sched: Fix remaining actions notification accounting issues
Date: Fri, 28 Aug 2026 23:10:12 +0000 [thread overview]
Message-ID: <178795861214.2836129.7637993004089359878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260824153903.4143642-1-victor@mojatatu.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Aug 2026 12:38:59 -0300 you wrote:
> Commit 8e2efb3f45a5 ("net/sched: add get_fill_size callbacks for actions
> missing them") fixed the reported echo/notify skb overrun and noted that
> the pre-existing issues Sashiko pointed out [1] would be fixed separately.
> This is that series.
>
> Patch 1 makes tcf_action_shared_attrs_size() a real upper bound again.
> TCA_ACT_IN_HW_COUNT and TCA_STATS_BASIC_HW are emitted on every action
> dump and were never budgeted; TCA_STATS_PKT64 was budgeted once but can be
> emitted twice; TCA_ACT_USED_HW_STATS and the rate estimator attributes are
> conditional and also unaccounted.
>
> [...]
Here is the summary with links:
- [net,1/4] net/sched: act_api: budget all shared attributes in notify skbs
https://git.kernel.org/netdev/net/c/13eb543cebef
- [net,2/4] net/sched: act_api: size the RTM_GETACTION reply from the actions
https://git.kernel.org/netdev/net/c/e9ca46ebc326
- [net,3/4] net/sched: act_api: fix skb sizing and action leak on reoffload delete
https://git.kernel.org/netdev/net/c/251367a0a331
- [net,4/4] net/sched: act_mirred: account for TCA_MIRRED_BLOCKID in get_fill_size
(no matching commit)
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-08-28 23:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 15:38 [PATCH net 0/4] net/sched: Fix remaining actions notification accounting issues Victor Nogueira
2026-08-24 15:39 ` [PATCH net 1/4] net/sched: act_api: budget all shared attributes in notify skbs Victor Nogueira
2026-08-27 8:44 ` Simon Horman
2026-08-27 18:37 ` Victor Nogueira
2026-08-24 15:39 ` [PATCH net 2/4] net/sched: act_api: size the RTM_GETACTION reply from the actions Victor Nogueira
2026-08-27 8:49 ` Simon Horman
2026-08-27 18:38 ` Victor Nogueira
2026-08-24 15:39 ` [PATCH net 3/4] net/sched: act_api: fix skb sizing and action leak on reoffload delete Victor Nogueira
2026-08-25 15:36 ` Pedro Tammela
2026-08-24 15:39 ` [PATCH net 4/4] net/sched: act_mirred: account for TCA_MIRRED_BLOCKID in get_fill_size Victor Nogueira
2026-08-27 8:53 ` Simon Horman
2026-08-27 18:39 ` Victor Nogueira
2026-08-27 9:24 ` Paolo Abeni
2026-08-27 18:40 ` Victor Nogueira
2026-08-28 23:10 ` 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=178795861214.2836129.7637993004089359878.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=baowen.zheng@corigine.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--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