blktests failures with v6.16 kernel

[Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>]

Hi all,

I ran the latest blktests (git hash: d24f7445c575) with the v6.16-rc1 kernel. I
observed 4 failures listed below. Comparing with the previous report with the
v6.16-rc1 kernel, there is no change in the list. All of the 4 failures are
still observed with the v6.16 kernel.

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

List of failures
================
#1: block/005
#2: nvme/041 (fc transport)
#3: nvme/061 failure (fc transport)
#4: nvme/063 failure (tcp transport)


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

#1: block/005

    When the test case is run for a NVME device as TEST_DEV, the kernel reports
    a lockdep WARN related to the three locks q->q_usage_counter, fs_reclaim and
    cpu_hotplug_lock. Refer to the report for the v6.16-rc1 kernel [1].

#2: nvme/041 (fc transport)

    The test case nvme/041 fails for fc transport. Refer to the report for the
    v6.12 kernel [2].

    [2] https://lore.kernel.org/linux-nvme/6crydkodszx5vq4ieox3jjpwkxtu7mhbohypy24awlo5w7f4k6@to3dcng24rd4/

#3: nvme/061 failure (fc transport)

    The test case nvme/061 sometimes fails for fc transport due to a WARN and
    refcount message "refcount_t: underflow; use-after-free." Refer to the
    report for the v6.15 kernel [3].

    [3] https://lore.kernel.org/linux-block/2xsfqvnntjx5iiir7wghhebmnugmpfluv6ef22mghojgk6gilr@mvjscqxroqqk/

#4: nvme/063 failure (tcp transport)

    The test case nvme/063 fails 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 report for the v6.16-rc1 kernel [1].