From: patchwork-bot+netdevbpf@kernel.org
To: Vlad Buslov <vladbu@nvidia.com>
Cc: pabeni@redhat.com, davem@davemloft.net, kuba@kernel.org,
jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
renmingshuai@huawei.com, netdev@vger.kernel.org,
liaichun@huawei.com, caowangbao@huawei.com, yanan@huawei.com,
liubo335@huawei.com, pctammela@mojatatu.com,
simon.horman@corigine.com
Subject: Re: [PATCH net] net/sched: cls_api: Fix lockup on flushing explicitly created chain
Date: Thu, 15 Jun 2023 06:10:20 +0000 [thread overview]
Message-ID: <168680942054.31160.1120307355113924275.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230612093426.2867183-1-vladbu@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 12 Jun 2023 11:34:26 +0200 you wrote:
> Mingshuai Ren reports:
>
> When a new chain is added by using tc, one soft lockup alarm will be
> generated after delete the prio 0 filter of the chain. To reproduce
> the problem, perform the following steps:
> (1) tc qdisc add dev eth0 root handle 1: htb default 1
> (2) tc chain add dev eth0
> (3) tc filter del dev eth0 chain 0 parent 1: prio 0
> (4) tc filter add dev eth0 chain 0 parent 1:
>
> [...]
Here is the summary with links:
- [net] net/sched: cls_api: Fix lockup on flushing explicitly created chain
https://git.kernel.org/netdev/net/c/c9a82bec02c3
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:[~2023-06-15 6:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 9:34 [PATCH net] net/sched: cls_api: Fix lockup on flushing explicitly created chain Vlad Buslov
2023-06-12 13:59 ` Pedro Tammela
2023-06-12 14:07 ` Vlad Buslov
2023-06-12 14:35 ` renmingshuai
2023-06-15 6: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=168680942054.31160.1120307355113924275.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=caowangbao@huawei.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liaichun@huawei.com \
--cc=liubo335@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=renmingshuai@huawei.com \
--cc=simon.horman@corigine.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yanan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.