[PATCH 0/2] nvme-tcp: lockdep: use dynamic lockdep keys per socket instance

[Keith Busch]

On Sat, May 30, 2026 at 02:20:43PM +0900, Shin'ichiro Kawasaki wrote:
> When NVMe-TCP controller setup and teardown are repeated with lockdep
> enabled, lockdep reports false-positive WARNs. This was observed when
> running blktests nvme/005 on v7.1-rc1 with a patch [1]. Analysis by
> Nilay [2] confirmed that the WARNs are false positives caused by lockdep
> confusing different socket instances due to shared static lockdep keys.
> 
> This series resolves the issue by using dynamically allocated lockdep
> keys per socket instance instead of static keys. This ensures lockdep
> correctly tracks locks across different socket instances. For that
> purpose, the first patch moves a function as preparation. The second
> patch introduces the dynamic lockdep keys.
> 
> [1] https://lore.kernel.org/linux-nvme/afB5syZbUrppgsDQ@shinmob/
> [2] https://lore.kernel.org/linux-nvme/c4ddc101-184a-4e4f-82ca-c3123bce5e34@linux.ibm.com/
> 
> Shin'ichiro Kawasaki (2):
>   nvme-tcp: move nvme_tcp_reclassify_socket()
>   nvme-tcp: lockdep: use dynamic lockdep keys per socket instance

Thanks, patch 1 is applied. Please have a look at my comment on patch 2
and let me know if we need to respin that version for it.