From: Pedro Tammela <pctammela@mojatatu.com>
To: Kyle Zeng <kylebot@openai.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Vlad Buslov <vladbu@nvidia.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/sched: act_api: use mutex in tcf_idr_check_alloc
Date: Wed, 27 May 2026 14:38:46 -0300 [thread overview]
Message-ID: <d1484ff7-2d81-4df4-87bf-ce9f9726eff8@mojatatu.com> (raw)
In-Reply-To: <20260526220847.28365-1-kylebot@openai.com>
On 26/05/2026 19:08, Kyle Zeng wrote:
> Currently, the NEWTFILTER path uses RCU to guard action idr accesses while
> the DELTFILTER path uses mutex to guard action accesses. This
> inconsistency leads to a race condition scenario, which can lead to
> erroneous operations on refcount, eventually leading to use-after-free
> situation.
> In this patch, we revert the introduction of RCU back to mutex in the
> NEWFILTER path, which is consistent with the DELFILTER path, avoiding
> the race condition.
>
> Fixes: 4b55e86736d5 ("net/sched: act_api: rely on rcu in tcf_idr_check_alloc")
> Signed-off-by: Kyle Zeng <kylebot@openai.com>
Reviewed-by: Pedro Tammela <pctammela@mojatatu.com>
> ---
> net/sched/act_api.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/net/sched/act_api.c b/net/sched/act_api.c
> index 332fd9695e54..63841c3e4310 100644
> --- a/net/sched/act_api.c
> +++ b/net/sched/act_api.c
> @@ -874,36 +874,34 @@ int tcf_idr_check_alloc(struct tc_action_net *tn, u32 *index,
> u32 max;
>
> if (*index) {
> - rcu_read_lock();
> + mutex_lock(&idrinfo->lock);
> p = idr_find(&idrinfo->action_idr, *index);
>
> if (IS_ERR(p)) {
> /* This means that another process allocated
> * index but did not assign the pointer yet.
> */
> - rcu_read_unlock();
> + mutex_unlock(&idrinfo->lock);
> return -EAGAIN;
> }
>
> if (!p) {
> /* Empty slot, try to allocate it */
> max = *index;
> - rcu_read_unlock();
> + mutex_unlock(&idrinfo->lock);
> goto new;
> }
>
> if (!refcount_inc_not_zero(&p->tcfa_refcnt)) {
> /* Action was deleted in parallel */
> - rcu_read_unlock();
> + mutex_unlock(&idrinfo->lock);
> return -EAGAIN;
> }
>
> if (bind)
> atomic_inc(&p->tcfa_bindcnt);
> *a = p;
> -
> - rcu_read_unlock();
> -
> + mutex_unlock(&idrinfo->lock);
> return 1;
> } else {
> /* Find a slot */
next prev parent reply other threads:[~2026-05-27 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 22:08 Kyle Zeng
2026-05-27 16:31 ` Jamal Hadi Salim
2026-05-27 17:38 ` Pedro Tammela [this message]
2026-05-28 12:21 ` Victor Nogueira
2026-05-29 1:13 ` Jakub Kicinski
2026-05-29 14:13 ` Jamal Hadi Salim
2026-05-29 23:15 ` Kyle Zeng
2026-05-30 11:49 ` Jamal Hadi Salim
2026-05-31 16:09 ` Jamal Hadi Salim
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=d1484ff7-2d81-4df4-87bf-ce9f9726eff8@mojatatu.com \
--to=pctammela@mojatatu.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=kylebot@openai.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladbu@nvidia.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
all inboxes | Powered by JetHome®