From: Paolo Abeni <pabeni@redhat.com>
To: Linkui Xiao <xiaolinkui@126.com>,
jhs@mojatatu.com, jiri@resnulli.us, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, horms@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Linkui Xiao <xiaolinkui@kylinos.cn>
Subject: Re: [PATCH net-next 1/3] net/sched: act_gact: size TCA_GACT_PROB unconditionally
Date: Thu, 12 Nov 2026 15:01:50 +0100 [thread overview]
Message-ID: <e4149337-b7d0-4797-8ec4-dab696af11c9@redhat.com> (raw)
In-Reply-To: <20261106064114.3592670-2-xiaolinkui@126.com>
On 11/6/26 07:41, Linkui Xiao wrote:
> From: Linkui Xiao <xiaolinkui@kylinos.cn>
>
> tcf_gact_get_fill_size() reads tcfg_ptype with neither tcfg_lock nor
> READ_ONCE(), and budgets TCA_GACT_PROB only when that read happens to be
> non-zero. Both halves are wrong.
>
> The bare read is a data race. tcf_gact_init() writes tcfg_ptype under
> spin_lock_bh(&gact->tcf_lock) when an action is replaced,
> tcf_gact_dump() re-reads it under the same lock, and tcf_gact_act()
> reads it with READ_ONCE(). get_fill_size() is the only accessor of the
> field with neither. act_bpf hit the same problem and solved it by
> taking tcf_lock in tcf_bpf_get_fill_size(), with a comment explaining
> why.
>
> The conditional budget breaks the rule that commit 4ba61bfd4998
> ("net/sched: add get_fill_size() to the five actions that lack one")
> spells out: "Size every optional attribute
> unconditionally: reading the current flags to size it conditionally
> would race a concurrent replace, which can flip the attributes between
> sizing and dumping." A replace that turns tcfg_ptype from zero into
> non-zero between the two calls leaves tcf_gact_dump() writing a
> TCA_GACT_PROB attribute -- nla_total_size(sizeof(struct tc_gact_p)) ==
> 12 bytes -- that was never budgeted.
>
> Size TCA_GACT_PROB unconditionally. The budget becomes an upper bound
> again and the bare read goes away, so unlike act_bpf this needs no lock.
>
> Nothing overflows today, so this is locking hygiene plus conformance to
> the rule above rather than a live bug. All four consumers of the value
> -- tcf_get_notify(), tcf_del_notify_msg(), tcf_add_notify_msg() and
> tcf_reoffload_del_notify_msg() -- allocate at least
> max(attr_size, NLMSG_GOODSIZE), and the delete and add paths add
> tcf_action_warn_attr_size(extack) on top. NLMSG_GOODSIZE is
> SKB_WITH_OVERHEAD(PAGE_SIZE), so a batch has to carry enough actions for
> attr_size to grow past roughly 3.7 KiB before a 12-byte shortfall
> matters -- which is the failure mode that commit 8e2efb3f45a5
> ("net/sched: add get_fill_size callbacks for actions missing them")
> fixed for other actions. A replace cannot interleave between sizing and
> dumping either: RTM_NEWACTION, RTM_DELACTION and RTM_GETACTION all take
> rtnl, and the classifier path, which can run without rtnl, computes
> attr_size in tcf_exts_validate_ex() and discards it.
>
> Tested by building with CONFIG_GACT_PROB=y so that the code being
> changed is actually compiled; net/sched builds with W=1 and no new
> warnings. Patch 3 adds TDC cases for the gact dump and get paths.
>
> Fixes: 9c5c9c573700 ("net sched actions: implement get_fill_size routine in act_gact")
As nothing really was broken, this and the next patch do not need a
fixes tag. I'll strip it when applying. Also next time please try
produce more terse changelogs.
/P
next prev parent reply other threads:[~2026-11-12 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 6:41 [PATCH net-next 0/3] net/sched: get_fill_size() budget fixes for act_gact and act_vlan Linkui Xiao
2026-11-06 6:41 ` [PATCH net-next 1/3] net/sched: act_gact: size TCA_GACT_PROB unconditionally Linkui Xiao
2026-11-12 14:01 ` Paolo Abeni [this message]
2026-11-06 6:41 ` [PATCH net-next 2/3] net/sched: act_vlan: size push_eth in get_fill_size Linkui Xiao
2026-11-06 6:41 ` [PATCH net-next 3/3] selftests: tc-testing: add gact probability dump tests Linkui Xiao
2026-11-12 14:05 ` Paolo Abeni
2026-11-12 14:20 ` [PATCH net-next 0/3] net/sched: get_fill_size() budget fixes for act_gact and act_vlan 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=e4149337-b7d0-4797-8ec4-dab696af11c9@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiaolinkui@126.com \
--cc=xiaolinkui@kylinos.cn \
/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
all inboxes | Powered by JetHome®