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

[Shin'ichiro Kawasaki]

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

 drivers/nvme/host/tcp.c | 88 +++++++++++++++++++++++------------------
 1 file changed, 49 insertions(+), 39 deletions(-)

-- 
2.54.0