blktests failures with v6.1

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

Hi all,

I ran the latest blktests (git hash: b35866f2d0df) with v6.1 kernel and
observed 5 test cases fail. I call for support to fix them.

List of failure cases
=====================
#1: block/011
#2: block/024
#3: nvme/002
#4: nvme/016
#5: nvme/017

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

#1: block/011

   The test case fails with NVME devices due to lockdep WARNING "possible
   circular locking dependency detected". Reported in September [1] and solution
   was discussed. A kernel fix patch was posted [2]. It may not be the best fix.

   [1] https://lore.kernel.org/linux-block/20220930001943.zdbvolc3gkekfmcv@shindev/
   [2] https://lore.kernel.org/linux-nvme/20221012080318.705449-1-shinichiro.kawasaki@wdc.com/

   This test case shows different failure symptom with HDDs. Need further
   investigation.

#2: block/024

   Fails on slow machines. I suspect test case needs improvement.
   Need further investigation.

   block/024 (do I/O faster than a jiffy and check iostats times) [failed]
    runtime    ...  4.347s
    --- tests/block/024.out     2022-12-06 20:51:41.525066605 +0900
    +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/block/024.out.bad       2022-12-07 12:51:03.610924521 +0900
    @@ -6,5 +6,5 @@
     read 1 s
     write 1 s
     read 2 s
    -write 3 s
    +write 4 s
     Test complete

#3: nvme/002
#4: nvme/016
#5: nvme/017

   The test cases fail with similar messages below. Reported in June [3].
   Fixes in the test cases are expected.

   [3] https://lore.kernel.org/linux-nvme/20220609235329.4jbz4wr3eg2nmzqa@shindev/

   nvme/002 (create many subsystems and test discovery)         [failed]
    runtime    ...  119.796s
    --- tests/nvme/002.out      2022-12-13 12:42:53.694306873 +0900
    +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/002.out.bad        2022-12-13 14:06:35.864050520 +0900
    @@ -1,3003 +1,3006 @@
     Running nvme/002
    -Discovery Log Number of Records 1000, Generation counter X
    +Discovery Log Number of Records 1001, Generation counter X
     =====Discovery Log Entry 0======
     trtype:  loop
    -subnqn:  blktests-subsystem-0
    +subnqn:  nqn.2014-08.org.nvmexpress.discovery
    ...
    (Run 'diff -u tests/nvme/002.out /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/002.out.bad' to see the entire diff)

   nvme/016 (create/delete many NVMeOF block device-backed ns and test discovery) [failed]
    runtime    ...  46.695s
    --- tests/nvme/016.out      2022-12-13 12:42:53.706306913 +0900
    +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/016.out.bad        2022-12-13 14:12:30.566239949 +0900
    @@ -1,6 +1,9 @@
     Running nvme/016
    -Discovery Log Number of Records 1, Generation counter X
    +Discovery Log Number of Records 2, Generation counter X
     =====Discovery Log Entry 0======
     trtype:  loop
    +subnqn:  nqn.2014-08.org.nvmexpress.discovery
    +=====Discovery Log Entry 1======
    ...
    (Run 'diff -u tests/nvme/016.out /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/016.out.bad' to see the entire diff)

   nvme/017 (create/delete many file-ns and test discovery)     [failed]
    runtime    ...  81.274s
    --- tests/nvme/017.out      2022-12-13 12:42:53.707306917 +0900
    +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/017.out.bad        2022-12-13 14:13:52.828515799 +0900
    @@ -1,6 +1,9 @@
     Running nvme/017
    -Discovery Log Number of Records 1, Generation counter X
    +Discovery Log Number of Records 2, Generation counter X
     =====Discovery Log Entry 0======
     trtype:  loop
    +subnqn:  nqn.2014-08.org.nvmexpress.discovery
    +=====Discovery Log Entry 1======
    ...
    (Run 'diff -u tests/nvme/017.out /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nvme/017.out.bad' to see the entire diff)

-- 
Shin'ichiro Kawasaki