blktests failures with v6.10 kernel
Shinichiro Kawasaki
shinichiro.kawasaki at wdc.com
Fri Jul 19 02:33:15 PDT 2024
Hi all,
I ran the latest blktests (git hash: f79783b44a5b) with the v6.10 kernel. Also I
checked the CKI project run results. In total, four failures were observed, as
listed below.
The nvme/050 failure observed with the kernel v6.10-rc1 [1] was fixed and no
longer observed. Good.
[1] https://lore.kernel.org/linux-block/wnucs5oboi4flje5yvtea7puvn6zzztcnlrfz3lpzlwgblrxgw@7wvqdzioejgl
List of failures
================
#1: nvme/041 (fc transport)
#2: dm/002
#3: srp/002 (siw driver)
#4: nbd/001,002 (CKI failure)
Failure description
===================
#1: 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 [2].
[2] https://lore.kernel.org/linux-nvme/20240221132404.6311-1-dwagner@suse.de/
#2: dm/002
When udev accesses the test target dm-dust device, "dmsetup remove" by the
test case fails. A fix patch for blktests is posted [3].
[3] https://lore.kernel.org/linux-block/20240719042318.265227-1-shinichiro.kawasaki@wdc.com/
#3: srp/002 (siw driver)
During the fix confirmation work of srp/002 hang with rxe driver, KASAN slab-
use-after-free was observed with siw driver [4]. Bart identified the resource
freed under use (thanks!). His kernel fix patch is queued for v6.11-rc1 [5].
[4] https://lore.kernel.org/linux-rdma/5prftateosuvgmosryes4lakptbxccwtx7yajoicjhudt7gyvp@w3f6nqdvurir/
[5] https://lore.kernel.org/linux-rdma/20240605145117.397751-6-bvanassche@acm.org/
#4: nbd/001,002
The CKI project reported that nbd/001 and nbd/002 fail occasionally. The
failure cause was the race between nbd-server port readiness and nbd-client
connect. A fix patch for blktests is posted [6].
[6] https://lore.kernel.org/linux-block/20240719050726.265769-1-shinichiro.kawasaki@wdc.com/
More information about the Linux-nvme
mailing list