From: patchwork-bot+netdevbpf@kernel.org
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, jhs@mojatatu.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
luoxuanqiang@kylinos.cn
Subject: Re: [PATCH net v1 0/2] net/sched: fix action batch failure cleanup
Date: Thu, 10 Sep 2026 16:20:09 +0000 [thread overview]
Message-ID: <178905720988.1524130.17486629819639799377.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909070336.32979-1-xuanqiang.luo@linux.dev>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Sep 2026 15:03:34 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> Failed batched RTM_NEWACTION requests can leak action references and
> reserved IDR indices when cleanup encounters a filter-bound action.
>
> Patch 1 fixes the failure cleanup.
>
> [...]
Here is the summary with links:
- [net,v1,1/2] net/sched: act_api: release all action references on NEWACTION failure
https://git.kernel.org/netdev/net/c/478eb5abb519
- [net,v1,2/2] selftests: tc-testing: test action batch failure cleanup
https://git.kernel.org/netdev/net/c/2a86bbed9f60
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-09-10 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 7:03 Xuanqiang Luo
2026-09-09 7:03 ` [PATCH net v1 1/2] net/sched: act_api: release all action references on NEWACTION failure Xuanqiang Luo
2026-09-09 7:03 ` [PATCH net v1 2/2] selftests: tc-testing: test action batch failure cleanup Xuanqiang Luo
2026-09-09 10:05 ` [PATCH net v1 0/2] net/sched: fix " Jamal Hadi Salim
2026-09-10 16:20 ` 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=178905720988.1524130.17486629819639799377.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luoxuanqiang@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=xuanqiang.luo@linux.dev \
/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®