The qemu-arm64, qemu-armv7 and qemu-riscv boot failed on Sasha Linus-next tree due to ext4 crash. Please find more details below
First seen on commit sha id c12cd257292c0c29463aa305967e64fc31a514d8. Good: 7ff71d62bdc4828b0917c97eb6caebe5f4c07220 Bad: d11b462aa01e0ffd5f8cc81bd5d2cfe4e48c8fbd
qemu-arm64: * boot/gcc-13-lkftconfig * boot/clang-nightly-lkftconfig * boot/gcc-13-lkftconfig-perf
qemu-armv7: * boot/gcc-13-lkftconfig * boot/clang-19-lkftconfig
qemu-riscv64: * boot/clang-19-lkftconfig * boot/gcc-13-lkftconfig
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Test log: --------- <4>[ 1.961480] __kmem_cache_create_args(ext4_groupinfo_4k) failed with error -22 <4>[ 1.962527] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc7 #1 <4>[ 1.963220] Hardware name: linux,dummy-virt (DT) <4>[ 1.964500] Call trace: <4>[ 1.964869] dump_backtrace (arch/arm64/kernel/stacktrace.c:321) <4>[ 1.966166] show_stack (arch/arm64/kernel/stacktrace.c:328) <4>[ 1.966570] dump_stack_lvl (lib/dump_stack.c:123) <4>[ 1.966998] dump_stack (lib/dump_stack.c:130) <4>[ 1.967331] __kmem_cache_create_args (mm/slab_common.c:363) <4>[ 1.967774] ext4_mb_init (include/linux/slab.h:349 fs/ext4/mballoc.c:3525 fs/ext4/mballoc.c:3614) <4>[ 1.968194] ext4_fill_super (fs/ext4/super.c:5543 fs/ext4/super.c:5717) <4>[ 1.968680] get_tree_bdev_flags (fs/super.c:1636) <4>[ 1.969043] get_tree_bdev (fs/super.c:1660) <4>[ 1.969370] ext4_get_tree (fs/ext4/super.c:5750) <4>[ 1.969781] vfs_get_tree (fs/super.c:1814) <4>[ 1.970174] path_mount (fs/namespace.c:3507 fs/namespace.c:3834) <4>[ 1.970592] init_mount (fs/init.c:25) <4>[ 1.970937] do_mount_root (init/do_mounts.c:165) <4>[ 1.971369] mount_root_generic (init/do_mounts.c:205) <4>[ 1.971782] mount_root (init/do_mounts.c:410) <4>[ 1.972175] prepare_namespace (init/do_mounts.c:493) <4>[ 1.972610] kernel_init_freeable (init/main.c:1593) <4>[ 1.973030] kernel_init (init/main.c:1473) <4>[ 1.973385] ret_from_fork (arch/arm64/kernel/entry.S:861) <0>[ 1.974278] EXT4-fs: no memory for groupinfo slab cache <3>[ 1.974889] EXT4-fs (vda): failed to initialize mballoc (-12) <3>[ 1.979727] EXT4-fs (vda): mount failed <4>[ 1.985849] VFS: Cannot open root device "/dev/vda" or unknown-block(254,0): error -12 <4>[ 1.986425] Please append a correct "root=" boot option; here are the available partitions: <4>[ 1.987344] fe00 2651632 vda <4>[ 1.987471] driver: virtio_blk <4>[ 1.988006] 1f00 131072 mtdblock0 <4>[ 1.988071] (driver?) <3>[ 1.988693] List of all bdev filesystems: <3>[ 1.989007] ext3 <3>[ 1.989089] ext2 <3>[ 1.989243] ext4 <3>[ 1.990678] squashfs <3>[ 1.990900] vfat <3>[ 1.991157] <0>[ 1.991778] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0) <4>[ 1.993227] CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc7 #1 <4>[ 1.994220] Hardware name: linux,dummy-virt (DT) <4>[ 1.994690] Call trace: <4>[ 1.994943] dump_backtrace (arch/arm64/kernel/stacktrace.c:321) <4>[ 1.995263] show_stack (arch/arm64/kernel/stacktrace.c:328) <4>[ 1.995478] dump_stack_lvl (lib/dump_stack.c:124) <4>[ 1.995802] dump_stack (lib/dump_stack.c:130) <4>[ 1.996206] panic (kernel/panic.c:354) <4>[ 1.996603] mount_root_generic (init/do_mounts.c:252) <4>[ 1.996964] mount_root (init/do_mounts.c:410) <4>[ 1.998083] prepare_namespace (init/do_mounts.c:493) <4>[ 1.998533] kernel_init_freeable (init/main.c:1593) <4>[ 1.998977] kernel_init (init/main.c:1473) <4>[ 1.999334] ret_from_fork (arch/arm64/kernel/entry.S:861) <2>[ 1.999930] SMP: stopping secondary CPUs <0>[ 2.001613] Kernel Offset: 0x25c315a00000 from 0xffff800080000000 <0>[ 2.001973] PHYS_OFFSET: 0x40000000 <0>[ 2.003672] CPU features: 0x00,0000000d,062f797c,677e7f3f <0>[ 2.005317] Memory Limit: none <0>[ 2.007534] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(254,0) ]---
Boot log: --------- - https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.11-15193-gd11b... - https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.11-15430-gc12c...
Build image: ----------- - https://storage.tuxsuite.com/public/linaro/lkft/builds/2owGnu3uAtzDsaiD2mLqc...
Steps to reproduce: ------------ - https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2owGobRSnVp... - https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/lkft/tests/2owGobRSnVp...
metadata: ---- Linux version: 6.12.0-rc7 git repo: https://git.kernel.org/pub/scm/linux/kernel/git/sashal/linus-next.git git sha: d11b462aa01e0ffd5f8cc81bd5d2cfe4e48c8fbd kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2owGnu3uAtzDsaiD2mLqc... build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2owGnu3uAtzDsaiD2mLqc... toolchain: gcc-13 and clang-19 config: gcc-13-lkftconfig arch: arm64
-- Linaro LKFT https://lkft.linaro.org
On Sat, 16 Nov 2024 at 22:51, Naresh Kamboju naresh.kamboju@linaro.org wrote:
The qemu-arm64, qemu-armv7 and qemu-riscv boot failed on Sasha Linus-next tree due to ext4 crash. Please find more details below
First seen on commit sha id c12cd257292c0c29463aa305967e64fc31a514d8. Good: 7ff71d62bdc4828b0917c97eb6caebe5f4c07220 Bad: d11b462aa01e0ffd5f8cc81bd5d2cfe4e48c8fbd
qemu-arm64:
- boot/gcc-13-lkftconfig
- boot/clang-nightly-lkftconfig
- boot/gcc-13-lkftconfig-perf
qemu-armv7:
- boot/gcc-13-lkftconfig
- boot/clang-19-lkftconfig
qemu-riscv64:
- boot/clang-19-lkftconfig
- boot/gcc-13-lkftconfig
The reported regressions have been fixed in latest commits on the sashal/linus-next.git tree.
- Naresh