Hi all, I ran the latest blktests (git hash: 80430afc5589) with the v6.11 kernel. This time, failures reported by the CKI project are not included in this report, since blktests run by the CKI project for the mainline kernel looks stopping since August. Comparing with the previous report using the v6.11-rc1 kernel [1], two failures were addressed. The srp/002 failure was fixed on the kernel side, and the nvme/052 failure was fixed on the blktests side. [1] https://lore.kernel.org/linux-block/5yal5unzvisrvfhhvsqrsqgu4tfbjp2fsrnbuyxioaxjgbojsi@o2arvhebzes3/ List of failures ================ #1: nvme/014 (tcp transport) #2: nvme/041 (fc transport) #3: scsi/008 Failure description =================== #1: nvme/014 (tcp transport) With the trtype=tcp configuration, nvme/014 fails occasionally with the kernel message "DEBUG_LOCKS_WARN_ON(lock->magic != lock)". It is rare, and 200 times of repeat is required to recreate the failure. A fix patch candidate was posted [2]. [2] https://lore.kernel.org/linux-nvme/20240912062707.1759715-1-shinichiro.kawasaki@xxxxxxx/ #2: nvme/041 (fc transport) With the trtype=fc configuration, nvme/041 fails: nvme/041 (Create authenticated connections) [failed] runtime 2.677s ... 4.823s --- tests/nvme/041.out 2023-11-29 12:57:17.206898664 +0900 +++ /home/shin/Blktests/blktests/results/nodev/nvme/041.out.bad 2024-03-19 14:50:56.399101323 +0900 @@ -2,5 +2,5 @@ Test unauthenticated connection (should fail) disconnected 0 controller(s) Test authenticated connection -disconnected 1 controller(s) +disconnected 0 controller(s) Test complete nvme/044 had same failure symptom until the kernel v6.9. A solution was suggested and discussed in Feb/2024 [3]. [3] https://lore.kernel.org/linux-nvme/20240221132404.6311-1-dwagner@xxxxxxx/ #3: scsi/008 Due to a kernel change, IO scheduler can not be changed to "none". Then the fio command with --ioscheduler=none option failed. A kernel fix patch was posted [4]. [4] https://lore.kernel.org/linux-block/20240917133231.134806-1-dlemoal@xxxxxxxxxx/
