blktests failures with v6.18 kernel

[Shinichiro Kawasaki]

Hi all,

It's a bit late, but I ran the latest blktests (git hash: 98dc6ad64c79) with the
v6.18 kernel. I observed 3 failures listed below. Comparing with the previous
report with the v6.18-rc1 kernel [1], 1 failure was fixed (nvme/014,057,058) and
no new other failure was observed.

[1] https://lore.kernel.org/linux-block/ynmi72x5wt5ooljjafebhcarit3pvu6axkslqenikb2p5txe57@ldytqa2t4i2x/


List of failures
================
#1: nvme/005,063 (tcp transport)
#2: nvme/041 (fc transport)
#3: nbd/002


Failure description
===================

#1: nvme/005,063 (tcp transport)

     The test case nvme/005 and 063 fail for tcp transport due to the lockdep
     WARN related to the three locks q->q_usage_counter, q->elevator_lock and
     set->srcu. Refer to the nvme/063 failure report for v6.16-rc1 kernel [2].

     [2] https://lore.kernel.org/linux-block/4fdm37so3o4xricdgfosgmohn63aa7wj3ua4e5vpihoamwg3ui@fq42f5q5t5ic/

#2: nvme/041 (fc transport)

     The test case nvme/041 fails for fc transport. Refer to the report for the
     v6.12 kernel [3]. Daniel posted the fix patch series [4].

     [3] https://lore.kernel.org/linux-nvme/6crydkodszx5vq4ieox3jjpwkxtu7mhbohypy24awlo5w7f4k6@to3dcng24rd4/
     [4] https://lore.kernel.org/linux-nvme/20250829-nvme-fc-sync-v3-0-d69c87e63aee@kernel.org/

#3: nbd/002

     The test case nbd/002 fails due to the lockdep WARN related to
     mm->mmap_lock, sk_lock-AF_INET6 and fs_reclaim. Refer to the nbd/002 failure
     report for v6.18-rc1 kernel [1].