From: patchwork-bot+netdevbpf@kernel.org
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, edumazet@google.com, horms@kernel.org,
jiri@resnulli.us, victor@mojatatu.com, security@kernel.org,
stable@vger.kernel.org, feng.xue@outlook.com, vladb@nvidia.com
Subject: Re: [PATCH] net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers
Date: Tue, 04 Aug 2026 14:40:05 +0000 [thread overview]
Message-ID: <178585440589.3186075.1456142899655290504.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260801125632.360365-1-jhs@mojatatu.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 1 Aug 2026 08:56:32 -0400 you wrote:
> Another challenge with unlocked filters.
> There is a short window in tc_new_tfilter where a tcf_proto can be found
> and briefly referenced by a totally unrelated, unlocked classifier's request
> and cause a race.
>
> Feng created a poc which created this race with two threads, one creating a
> u32 filter and other a flower filter in the same chain/prio:
>
> [...]
Here is the summary with links:
- net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers
https://git.kernel.org/netdev/net/c/a347304b2ca1
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-04 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 12:56 [PATCH] net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers Jamal Hadi Salim
2026-08-04 14:40 ` 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=178585440589.3186075.1456142899655290504.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=feng.xue@outlook.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@kernel.org \
--cc=stable@vger.kernel.org \
--cc=victor@mojatatu.com \
--cc=vladb@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