osandov
nvme/065: add nvme format test with supported LBA format
@yizhanglinux Thanks for this PR. With a first look, this test case looks useful for me. I tried to run the test case for a QEMU NVME device on the kernel v6.16-rc3 applying the patch series titled "fix atomic limits check v2". I observed a lockdep WARN at the first run. More importantly, I observed the test case hang at the 2nd run. For recording, I upload dmesg observed at the WARN and the hang. dmesg.txt
Yi, do you expect the WARN the hang?
@yizhanglinux Thanks for this PR. With a first look, this test case looks useful for me. I tried to run the test case for a QEMU NVME device on the kernel v6.16-rc3 applying the patch series titled "fix atomic limits check v2". I observed a lockdep WARN at the first run. More importantly, I observed the test case hang at the 2nd run. For recording, I upload dmesg observed at the WARN and the hang. dmesg.txt
Yi, do you expect the WARN the hang?
Yeah, seems the test found new issue on kernel side, I didn't find such failure before, let me retest it on the latest linux-block/for-next now.
I tried 6 NVMe disks with the latest linux-block/for-next and didn't reproduce the WARNING/hang issue, bug there is one intel NVMe SSD, it reports supported lbaf0 to lbaf6, but the format operation failed with most of the lbaf, maybe there is FW issue with it.
# nvme list
Node Generic SN Model Namespace Usage Format FW Rev
--------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- --------
/dev/nvme0n1 /dev/ng0n1 S39WNA0K201139 Dell Express Flash PM1725a 1.6TB AIC 0x1 1.60 TB / 1.60 TB 4 KiB + 8 B 1.2.1
/dev/nvme1n1 /dev/ng1n1 S795NC0X201793 SAMSUNG MZWLO1T9HCJR-00A07 0x1 0.00 B / 1.92 TB 512 B + 0 B OPPA4B5Q
/dev/nvme2n1 /dev/ng2n1 2135312ADFD1 Micron_9300_MTFDHAL3T8TDP 0x1 3.84 TB / 3.84 TB 512 B + 0 B 11300DY0
/dev/nvme3n1 /dev/ng3n1 S64FNE0R802879 SAMSUNG MZQL2960HCJR-00A07 0x1 960.20 GB / 960.20 GB 4 KiB + 0 B GDC5302Q
/dev/nvme4n1 /dev/ng4n1 CVFT6011001V1P6DGN INTEL SSDPEDMD016T4 0x1 1.60 TB / 1.60 TB 512 B + 0 B 8DV10171
/dev/nvme5n1 /dev/ng5n1 3F50A00H0LR3 KIOXIA KCMYDRUG1T92 0x1 0.00 B / 1.92 TB 512 B + 0 B 1UET7104
# ./check nvme/065
nvme/065 => nvme0n1 (Test nvme format NVMe disk with supported LBA format) [passed]
runtime 3.004s ... 3.009s
nvme/065 => nvme2n1 (Test nvme format NVMe disk with supported LBA format) [passed]
runtime 11.128s ... 11.164s
nvme/065 => nvme3n1 (Test nvme format NVMe disk with supported LBA format) [passed]
runtime 2.114s ... 2.121s
nvme/065 => nvme4n1 (Test nvme format NVMe disk with supported LBA format) [failed]
runtime 40.918s ... 41.772s
--- tests/nvme/065.out 2025-06-27 03:05:27.324156330 -0400
+++ /root/blktests/results/nvme4n1/nvme/065.out.bad 2025-06-27 04:40:34.653108677 -0400
@@ -1,2 +1,12 @@
Running nvme/065
+NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
+/dev/nvme4n1 formatted to lbaf:0, expected:1
+NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
+/dev/nvme4n1 formatted to lbaf:0, expected:2
+NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
+/dev/nvme4n1 formatted to lbaf:3, expected:4
...
(Run 'diff -u tests/nvme/065.out /root/blktests/results/nvme4n1/nvme/065.out.bad' to see the entire diff)
nvme/065 => nvme5n1 (Test nvme format NVMe disk with supported LBA format) [passed]
runtime 2.775s ... 6.236s
# nvme id-ns /dev/nvme4n1 | tail -7
lbaf 0 : ms:0 lbads:9 rp:0x2 (in use)
lbaf 1 : ms:8 lbads:9 rp:0x2
lbaf 2 : ms:16 lbads:9 rp:0x2
lbaf 3 : ms:0 lbads:12 rp:0
lbaf 4 : ms:8 lbads:12 rp:0
lbaf 5 : ms:64 lbads:12 rp:0
lbaf 6 : ms:128 lbads:12 rp:0
# cat results/nvme4n1/nvme/065.full
Success formatting namespace:ffffffff
Success formatting namespace:ffffffff
Success formatting namespace:ffffffff
# cat results/nvme4n1/nvme/065.out.bad
Running nvme/065
NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
/dev/nvme4n1 formatted to lbaf:0, expected:1
NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
/dev/nvme4n1 formatted to lbaf:0, expected:2
NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
/dev/nvme4n1 formatted to lbaf:3, expected:4
NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
/dev/nvme4n1 formatted to lbaf:3, expected:5
NVMe status: Invalid Format: The LBA Format specified is not supported(0x10a)
/dev/nvme4n1 formatted to lbaf:3, expected:6
Test complete
Today, I tried to run the test with v6.17-rc5 kernel. When repeated the test case for 4kb block size QEMU NVME device, the kernel hanged: dmesg_Oct_3_2025.txt
This symptom is similar as the one I observed in June, so I guess the same cause still exists. udev-worker calls munmap() system call, then a Oops happens.