From: patchwork-bot+netdevbpf@kernel.org
To: Davide Caratti <dcaratti@redhat.com>
Cc: jhs@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] net/sched: don't use dynamic lockdep keys with clsact/ingress/noqueue
Date: Thu, 05 Feb 2026 17:50:05 +0000 [thread overview]
Message-ID: <177031380558.510957.10572633042146921098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <94448f7fa7c4f52d2ce416a4895ec87d456d7417.1770220576.git.dcaratti@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Feb 2026 17:02:31 +0100 you wrote:
> Currently we are registering one dynamic lockdep key for each allocated
> qdisc, to avoid false deadlock reports when mirred (or TC eBPF) redirects
> packets to another device while the root lock is acquired [1].
> Since dynamic keys are a limited resource, we can save them at least for
> qdiscs that are not meant to acquire the root lock in the traffic path,
> or to carry traffic at all, like:
>
> [...]
Here is the summary with links:
- [net-next,v2] net/sched: don't use dynamic lockdep keys with clsact/ingress/noqueue
https://git.kernel.org/netdev/net-next/c/a90f6dcefca6
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-02-05 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 16:02 [PATCH net-next v2] net/sched: don't use dynamic lockdep keys with clsact/ingress/noqueue Davide Caratti
2026-02-05 17:50 ` 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=177031380558.510957.10572633042146921098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=edumazet@google.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=xiyou.wangcong@gmail.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