next-20250915: LTP chdir01 df01_sh stat04 tst_device.c:97: TBROK: Could not stat loop device 0
The following LTP chdir01 df01_sh and stat04 tests failed on the rock-pi-4b qemu-arm64 on the Linux next-20250915 tag build.
First seen on next-20250915 Good: next-20250912 Bad: next-20250915
Regression Analysis: - New regression? yes - Reproducibility? yes
* rk3399-rock-pi-4b, ltp-smoke * qemu-arm64, ltp-smoke * qemu-arm64-compat, ltp-smoke - chdir01 - df01_sh - stat04
Test regression: next-20250915: LTP chdir01 df01_sh stat04 tst_device.c:97: TBROK: Could not stat loop device 0
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
## Test log <8>[ 53.655971] <LAVA_SIGNAL_STARTTC chdir01> tst_buffers.c:57: TINFO: Test is using guarded buffers tst_tmpdir.c:316: TINFO: Using /tmp/LTP_chdm4pHJb as tmpdir (tmpfs filesystem) tst_device.c:98: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1953: TINFO: LTP version: 20250530 tst_test.c:1956: TINFO: Tested kernel: 6.17.0-rc6-next-20250915 #1 SMP PREEMPT @1757983656 aarch64 tst_kconfig.c:88: TINFO: Parsing kernel config '/proc/config.gz' tst_kconfig.c:676: TINFO: CONFIG_TRACE_IRQFLAGS kernel option detected which might slow the execution tst_test.c:1774: TINFO: Overall timeout per run is 0h 28m 48s tst_supported_fs_types.c:97: TINFO: Kernel supports ext2 tst_supported_fs_types.c:62: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:97: TINFO: Kernel supports ext3 tst_supported_fs_types.c:62: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:97: TINFO: Kernel supports ext4 tst_supported_fs_types.c:62: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:128: TINFO: Filesystem xfs is not supported tst_supported_fs_types.c:97: TINFO: Kernel supports btrfs tst_supported_fs_types.c:62: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:105: TINFO: Skipping bcachefs because of FUSE blacklist tst_supported_fs_types.c:97: TINFO: Kernel supports vfat tst_supported_fs_types.c:62: TINFO: mkfs.vfat does exist tst_supported_fs_types.c:128: TINFO: Filesystem exfat is not supported tst_supported_fs_types.c:132: TINFO: FUSE does support ntfs tst_supported_fs_types.c:62: TINFO: mkfs.ntfs does exist tst_supported_fs_types.c:97: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:49: TINFO: mkfs is not needed for tmpfs tst_test.c:1888: TINFO: === Testing on ext2 === tst_device.c:391: TWARN: Failed to clear 512k block on /dev/loop0 tst_test.c:1217: TBROK: tst_clear_device() failed Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 tst_device.c:283: TWARN: open(/dev/loop0) failed: ENOENT (2) <8>[ 53.679564] <LAVA_SIGNAL_ENDTC chdir01> <8>[ 53.708246] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=chdir01 RESULT=fail>
<8>[ 53.933883] <LAVA_SIGNAL_STARTTC stat04> tst_buffers.c:57: TINFO: Test is using guarded buffers tst_tmpdir.c:316: TINFO: Using /tmp/LTP_staPDxElt as tmpdir (tmpfs filesystem) tst_device.c:97: TBROK: Could not stat loop device 0 Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <8>[ 53.947889] <LAVA_SIGNAL_ENDTC stat04> <8>[ 53.974024] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=stat04 RESULT=fail>
<8>[ 54.048075] <LAVA_SIGNAL_STARTTC df01_sh> df01 1 TINFO: Running: df01.sh df01 1 TINFO: Tested kernel: Linux runner-j2nyww-sk-project-40964107-concurrent-0 6.17.0-rc6-next-20250915 #1 SMP PREEMPT @1757983656 aarch64 GNU/Linux df01 1 TINFO: Using /tmp/LTP_df01.7pcwUXe1CN as tmpdir (tmpfs filesystem) tst_device.c:97: TBROK: Could not stat loop device 0 df01 1 TBROK: Failed to acquire device Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <8>[ 54.060936] <LAVA_SIGNAL_ENDTC df01_sh> <8>[ 54.087630] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=df01_sh RESULT=fail>
## Source * Kernel version: 6.17.0-rc6 * Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git * Git describe: 6.17.0-rc6-next-20250915 * Git commit: c3067c2c38316c3ef013636c93daa285ee6aaa2e * Architectures: arm64 * Toolchains: gcc-13 and gcc-8 * Kconfigs: lkftconfigs
## Build * Test log: https://qa-reports.linaro.org/api/testruns/29896973/log_file/ * Test details: https://regressions.linaro.org/lkft/linux-next-master/next-20250915/ltp-smok... * Test plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/32l4Vv9hKep... * Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UF8KltAzu6kUpW3hX... * Kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UF8KltAzu6kUpW3hX...
-- Linaro LKFT
On Tue 16-09-25 12:57:26, Naresh Kamboju wrote:
The following LTP chdir01 df01_sh and stat04 tests failed on the rock-pi-4b qemu-arm64 on the Linux next-20250915 tag build.
First seen on next-20250915 Good: next-20250912 Bad: next-20250915
Regression Analysis:
- New regression? yes
- Reproducibility? yes
- rk3399-rock-pi-4b, ltp-smoke
- qemu-arm64, ltp-smoke
- qemu-arm64-compat, ltp-smoke
- chdir01
- df01_sh
- stat04
Test regression: next-20250915: LTP chdir01 df01_sh stat04 tst_device.c:97: TBROK: Could not stat loop device 0
This is really strange. Those failing tests all start to complain that /dev/loop0 doesn't exist (open gets ENOENT)... The fact that this is limited to only a few archs suggests it's some race somewhere but I don't see any relevant changes in linux-block in last three days...
Honza
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
## Test log <8>[ 53.655971] <LAVA_SIGNAL_STARTTC chdir01> tst_buffers.c:57: TINFO: Test is using guarded buffers tst_tmpdir.c:316: TINFO: Using /tmp/LTP_chdm4pHJb as tmpdir (tmpfs filesystem) tst_device.c:98: TINFO: Found free device 0 '/dev/loop0' tst_test.c:1953: TINFO: LTP version: 20250530 tst_test.c:1956: TINFO: Tested kernel: 6.17.0-rc6-next-20250915 #1 SMP PREEMPT @1757983656 aarch64 tst_kconfig.c:88: TINFO: Parsing kernel config '/proc/config.gz' tst_kconfig.c:676: TINFO: CONFIG_TRACE_IRQFLAGS kernel option detected which might slow the execution tst_test.c:1774: TINFO: Overall timeout per run is 0h 28m 48s tst_supported_fs_types.c:97: TINFO: Kernel supports ext2 tst_supported_fs_types.c:62: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:97: TINFO: Kernel supports ext3 tst_supported_fs_types.c:62: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:97: TINFO: Kernel supports ext4 tst_supported_fs_types.c:62: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:128: TINFO: Filesystem xfs is not supported tst_supported_fs_types.c:97: TINFO: Kernel supports btrfs tst_supported_fs_types.c:62: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:105: TINFO: Skipping bcachefs because of FUSE blacklist tst_supported_fs_types.c:97: TINFO: Kernel supports vfat tst_supported_fs_types.c:62: TINFO: mkfs.vfat does exist tst_supported_fs_types.c:128: TINFO: Filesystem exfat is not supported tst_supported_fs_types.c:132: TINFO: FUSE does support ntfs tst_supported_fs_types.c:62: TINFO: mkfs.ntfs does exist tst_supported_fs_types.c:97: TINFO: Kernel supports tmpfs tst_supported_fs_types.c:49: TINFO: mkfs is not needed for tmpfs tst_test.c:1888: TINFO: === Testing on ext2 === tst_device.c:391: TWARN: Failed to clear 512k block on /dev/loop0 tst_test.c:1217: TBROK: tst_clear_device() failed Summary: passed 0 failed 0 broken 1 skipped 0 warnings 1 tst_device.c:283: TWARN: open(/dev/loop0) failed: ENOENT (2) <8>[ 53.679564] <LAVA_SIGNAL_ENDTC chdir01> <8>[ 53.708246] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=chdir01 RESULT=fail>
<8>[ 53.933883] <LAVA_SIGNAL_STARTTC stat04> tst_buffers.c:57: TINFO: Test is using guarded buffers tst_tmpdir.c:316: TINFO: Using /tmp/LTP_staPDxElt as tmpdir (tmpfs filesystem) tst_device.c:97: TBROK: Could not stat loop device 0 Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <8>[ 53.947889] <LAVA_SIGNAL_ENDTC stat04> <8>[ 53.974024] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=stat04 RESULT=fail>
<8>[ 54.048075] <LAVA_SIGNAL_STARTTC df01_sh> df01 1 TINFO: Running: df01.sh df01 1 TINFO: Tested kernel: Linux runner-j2nyww-sk-project-40964107-concurrent-0 6.17.0-rc6-next-20250915 #1 SMP PREEMPT @1757983656 aarch64 GNU/Linux df01 1 TINFO: Using /tmp/LTP_df01.7pcwUXe1CN as tmpdir (tmpfs filesystem) tst_device.c:97: TBROK: Could not stat loop device 0 df01 1 TBROK: Failed to acquire device Summary: passed 0 failed 0 broken 1 skipped 0 warnings 0 <8>[ 54.060936] <LAVA_SIGNAL_ENDTC df01_sh> <8>[ 54.087630] <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=df01_sh RESULT=fail>
## Source
- Kernel version: 6.17.0-rc6
- Git tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next.git
- Git describe: 6.17.0-rc6-next-20250915
- Git commit: c3067c2c38316c3ef013636c93daa285ee6aaa2e
- Architectures: arm64
- Toolchains: gcc-13 and gcc-8
- Kconfigs: lkftconfigs
## Build
- Test log: https://qa-reports.linaro.org/api/testruns/29896973/log_file/
- Test details:
https://regressions.linaro.org/lkft/linux-next-master/next-20250915/ltp-smok...
- Test plan: https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/32l4Vv9hKep...
- Build link: https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UF8KltAzu6kUpW3hX...
- Kernel config:
https://storage.tuxsuite.com/public/linaro/lkft/builds/32l4UF8KltAzu6kUpW3hX...
-- Linaro LKFT
On Tue 16-09-25 13:04:42, Jan Kara wrote:
On Tue 16-09-25 12:57:26, Naresh Kamboju wrote:
The following LTP chdir01 df01_sh and stat04 tests failed on the rock-pi-4b qemu-arm64 on the Linux next-20250915 tag build.
First seen on next-20250915 Good: next-20250912 Bad: next-20250915
Regression Analysis:
- New regression? yes
- Reproducibility? yes
- rk3399-rock-pi-4b, ltp-smoke
- qemu-arm64, ltp-smoke
- qemu-arm64-compat, ltp-smoke
- chdir01
- df01_sh
- stat04
Test regression: next-20250915: LTP chdir01 df01_sh stat04 tst_device.c:97: TBROK: Could not stat loop device 0
This is really strange. Those failing tests all start to complain that /dev/loop0 doesn't exist (open gets ENOENT)... The fact that this is limited to only a few archs suggests it's some race somewhere but I don't see any relevant changes in linux-block in last three days...
Ha, Mark Brown tracked this [1] to changes in VFS tree in extensible_ioctl_valid(). More discussion there I guess.
[1] https://lore.kernel.org/all/02da33e3-6583-4344-892f-a9784b9c5b1b@sirena.org....
Honza
On Tue, 16 Sept 2025 at 17:04, Jan Kara jack@suse.cz wrote:
On Tue 16-09-25 13:04:42, Jan Kara wrote:
On Tue 16-09-25 12:57:26, Naresh Kamboju wrote:
The following LTP chdir01 df01_sh and stat04 tests failed on the rock-pi-4b qemu-arm64 on the Linux next-20250915 tag build.
First seen on next-20250915 Good: next-20250912 Bad: next-20250915
Regression Analysis:
- New regression? yes
- Reproducibility? yes
- rk3399-rock-pi-4b, ltp-smoke
- qemu-arm64, ltp-smoke
- qemu-arm64-compat, ltp-smoke
- chdir01
- df01_sh
- stat04
Test regression: next-20250915: LTP chdir01 df01_sh stat04 tst_device.c:97: TBROK: Could not stat loop device 0
This is really strange. Those failing tests all start to complain that /dev/loop0 doesn't exist (open gets ENOENT)... The fact that this is limited to only a few archs suggests it's some race somewhere but I don't see any relevant changes in linux-block in last three days...
Ha, Mark Brown tracked this [1] to changes in VFS tree in extensible_ioctl_valid(). More discussion there I guess.
That right, Ander’s bisection confirmed the same commit that Mark Brown reported.
# first bad commit: [60949057a2e71c9244e82608adf269e62e6ac443] block: use extensible_ioctl_valid()
[1] https://lore.kernel.org/all/02da33e3-6583-4344-892f-a9784b9c5b1b@sirena.org....
Honza-- Jan Kara jack@suse.com SUSE Labs, CR
- Naresh
-
Jan Kara -
Naresh Kamboju