I've started to work on expanding coverage of testing with blktests on kdevops [0] to other test groups. srp was one of them. But the amount of failures I'm seeing seems to tell me I'm probably doing something really stupid, so please help me review the setup. The baseline for srp is listed below, each of these is a failure. I've used v5.17-rc7 as a starting point. You should able to reproduce the failure by creating a KVM guest with kdevops, confuguring the kernel to test to be v5.17-rc7 and then then running the following to bring up the guest: make menuconfig # enable blktests and just enable srp as the only guest make make bringup # bring up your guests make linux # compile and install v5.17-rc7 with all of blktests deps on guests make blktests # compile and install blktest as well as set up srp deps on guests make blktests-baseline # This runs the srp tests Or you can just skip the last step and run the test manually. The hosts created use a prefix based on CONFIG_KDEVOPS_HOSTS_PREFIX. On a system with this: grep CONFIG_KDEVOPS_HOSTS_PREFIX .config CONFIG_KDEVOPS_HOSTS_PREFIX="linux517" I then just ssh linux-517-blktests-srp sudo su - cd /usr/local/blktests ./check srp Note: if you enabled more than the srp guest you can also just run the test for that guest as follows: make blktests-baseline HOSTS=linux-517-blktests-srp Likewise on the host you can inspect the console: sudo virsh vagrant_linux-517-blktests-srp The failures I can rerproduce easily (and if not just run the test twice): srp/001 # failure rate is 1 always fails soft lockup https://gist.github.com/mcgrof/f94ad51123cfdbff4520a9964c292c2c srp/002 # failure rate is 1 always fails with an NMI https://gist.github.com/mcgrof/9f3b1b9592d2196eb79f8c22238dbfd9 srp/005 # failure rate is 1 always fails with an NMI https://gist.github.com/mcgrof/d73bc3c0fe91fbbf6d4b9957e51b3ddb srp/006 # failure rate is 1 always fails with a diff srp/007 # failure rate is 1 always fails with a diff srp/008 # failure rate is 1 always fails with a diff srp/009 # failure rate is 1 always fails with a soft lockup https://gist.github.com/mcgrof/d6b351b40f2345dd20a7fa8acee3f704 srp/010 # failure rate is 1 always fails with a diff srp/011 # failure rate is 1 always fails with an NMI https://gist.github.com/mcgrof/8f80e72f9f3bae20dcc3d45a06f30379 srp/012 # failure rate is 1 always fails with an NMI https://gist.github.com/mcgrof/72929570da5de920d9a37cb401225822 srp/013 # failure rate is 1 always fails with an NMI https://gist.github.com/mcgrof/eed4d4683fa53960bffc10c3c4fe1fda srp/014 # failure rate is 1 always fails with a diff To see the status of any host you can run on the host the blktests kdevops watchdog output manually, for instance I get: ./scripts/workflows/blktests/blktests_watchdog.py hosts baseline Hostname Test-name Completion % runtime(s) last-runtime(s) Stall-status Kernel linux517-blktests-block block/004 0% 13 0 OK 5.17.0-rc7 linux517-blktests-loop None 0% 0 0 OK 5.17.0-rc7 linux517-blktests-nbd None 0% 0 0 OK 5.17.0-rc7 linux517-blktests-nvme None 0% 0 0 OK 5.17.0-rc7 linux517-blktests-nvmemp None 0% 0 0 OK 5.17.0-rc7 linux517-blktests-scsi None 0% 0 0 OK 5.17.0-rc7 linux517-blktests-srp None 0% 0 0 Hung-Stalled Uname-issue linux517-blktests-zbd zbd/006 0% 32 0 OK 5.17.0-rc7 [0] https://github.com/mcgrof/kdevops.git LUis
