blktests throtl/002/003/007 failure on aarch64 platform with 64k kernel #220
Description
this issue happened on aarch64 platform with 64k kernel,
throtl/002/003/007 test failure on 64KB paged system, getconf PAGE_SIZE retrieves 65536 bytes as the sector_size and passes it to scsi_debug, but scsi_debug only supports a maximum sector_size of 4096 bytes, causing the module to fail to load and return the error "invalid sector_size 65536".
# uname -r
5.14.0-639.el9.aarch64+64k
# ./check throtl/002 throtl/003 throtl/007
throtl/002 (nullb) (iops limit over IO split) [passed]
runtime ... 3.103s
throtl/002 (sdebug) (iops limit over IO split) [failed]
runtime ... 0.776s
--- tests/throtl/002.out 2025-11-28 03:05:30.753102288 -0500
+++ /root/blktests/results/nodev_sdebug/throtl/002.out.bad 2025-11-28 03:35:59.503733888 -0500
@@ -1,4 +1,3 @@
Running throtl/002
-1
-1
-Test complete
+modprobe: ERROR: could not insert 'scsi_debug': Invalid argument
+Loading scsi_debug dev_size_mb=1024 delay=0 sector_size=65536 failed
throtl/003 (nullb) (bps limit over IO split) [passed]
runtime ... 2.838s
throtl/003 (sdebug) (bps limit over IO split) [failed]
runtime ... 0.175s
--- tests/throtl/003.out 2025-11-28 03:05:30.753102288 -0500
+++ /root/blktests/results/nodev_sdebug/throtl/003.out.bad 2025-11-28 03:36:02.583751799 -0500
@@ -1,4 +1,3 @@
Running throtl/003
-1
-1
-Test complete
+modprobe: ERROR: could not insert 'scsi_debug': Invalid argument
+Loading scsi_debug dev_size_mb=1024 delay=0 sector_size=65536 failed
throtl/007 (nullb) (bps limit with iops limit over io split) [passed]
runtime ... 4.835s
throtl/007 (sdebug) (bps limit with iops limit over io split) [failed]
runtime ... 0.196s
--- tests/throtl/007.out 2025-11-28 03:05:30.753102288 -0500
+++ /root/blktests/results/nodev_sdebug/throtl/007.out.bad 2025-11-28 03:36:07.683781456 -0500
@@ -1,6 +1,3 @@
Running throtl/007
-1
-2
-1
-2
-Test complete
+modprobe: ERROR: could not insert 'scsi_debug': Invalid argument
...
(Run 'diff -u tests/throtl/007.out /root/blktests/results/nodev_sdebug/throtl/007.out.bad' to see the entire diff)
[25662.805706] run blktests throtl/002 at 2025-11-28 03:35:55
[25662.818728] null_blk: disk dev_nullb created
[25665.942112] run blktests throtl/002 at 2025-11-28 03:35:58
[25666.218858] sd 48:0:0:0: [sda] Synchronizing SCSI cache
[25666.567390] scsi_debug:scsi_debug_init: invalid sector_size 65536
[25666.751050] run blktests throtl/003 at 2025-11-28 03:35:59
[25666.767936] null_blk: disk nullb0 created
[25666.767940] null_blk: module loaded
[25666.771786] null_blk: disk dev_nullb created
[25669.623433] run blktests throtl/003 at 2025-11-28 03:36:02
[25669.673555] scsi_debug:scsi_debug_init: invalid sector_size 65536
[25669.834615] run blktests throtl/007 at 2025-11-28 03:36:02
[25669.851694] null_blk: disk nullb0 created
[25669.851699] null_blk: module loaded
[25669.855527] null_blk: disk dev_nullb created
[25674.702199] run blktests throtl/007 at 2025-11-28 03:36:07
[25674.753499] scsi_debug:scsi_debug_init: invalid sector_size 65536
I tested sector_size as follows:（512 1024 2048 4096 8192 16384 32768 65536），
and scsi_debug create failed when the sector_size greater than 4096,
modprobe scsi_debug sector_size=$size delay=0
[14169.645012] scsi_debug:scsi_debug_init: invalid sector_size 8192
[14171.419707] scsi_debug:scsi_debug_init: invalid sector_size 16384
[14173.139453] scsi_debug:scsi_debug_init: invalid sector_size 32768
[14174.884545] scsi_debug:scsi_debug_init: invalid sector_size 65536
[14176.650099] scsi_debug:scsi_debug_init: invalid sector_size 65536