netdev - Re: [PATCH net-next v2] net/sched: don't use dynamic lockdep keys with clsact/ingress/noqueue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <177031380558.510957.10572633042146921098.git-patchwork-notify@kernel.org>
Date: Thu, 05 Feb 2026 17:50:05 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Davide Caratti <dcaratti@...hat.com>
Cc: jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 horms@...nel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2] net/sched: don't use dynamic lockdep keys
 with
 clsact/ingress/noqueue

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.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