[moderation] [fs?] upstream test error: kernel panic: VFS: Unable to mount root fs on "/dev/vda" or unknown-block(NUM,NUM)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 552c50713f27 Merge tag 'vfio-v6.18-rc3' of https://github...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10757c58580000
kernel config: https://syzkaller.appspot.com/x/.config?x=390308a9d04aa4a5
dashboard link: https://syzkaller.appspot.com/bug?extid=86d550f41ba3ad62e664
compiler: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/fa3fbcfdac58/non_bootable_disk-552c5071.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a038f45e95e2/vmlinux-552c5071.xz
kernel image: https://storage.googleapis.com/syzbot-assets/96e338f97594/zImage-552c5071.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+86d550...@syzkaller.appspotmail.com

PM: genpd: Disabling unused power domains
ALSA device list:
#0: Dummy 1
#1: Loopback 1
#2: Virtual MIDI Card 1
check access for rdinit=/init failed: -2, ignoring
md: Skipping autodetection of RAID arrays. (raid=autodetect will force)
List of all partitions:
0100 4096 ram0
(driver?)
0101 4096 ram1
(driver?)
0102 4096 ram2
(driver?)
0103 4096 ram3
(driver?)
0104 4096 ram4
(driver?)
0105 4096 ram5
(driver?)
0106 4096 ram6
(driver?)
0107 4096 ram7
(driver?)
0108 4096 ram8
(driver?)
0109 4096 ram9
(driver?)
010a 4096 ram10
(driver?)
010b 4096 ram11
(driver?)
010c 4096 ram12
(driver?)
010d 4096 ram13
(driver?)
010e 4096 ram14
(driver?)
010f 4096 ram15
(driver?)
fd00 1048576 vda
driver: virtio_blk
fa00 262144000 nullb0
(driver?)
1f00 131072 mtdblock0
(driver?)
1f01 128 mtdblock1
(driver?)
No filesystem could mount root, tried:
fuseblk
Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/vda" or unknown-block(253,0)
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted syzkaller #0 PREEMPT
Hardware name: linux,dummy-virt (DT)
Call trace:
show_stack+0x18/0x24 arch/arm64/kernel/stacktrace.c:499 (C)
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x38/0xf4 lib/dump_stack.c:120
dump_stack+0x1c/0x28 lib/dump_stack.c:129
vpanic+0x49c/0x50c kernel/panic.c:489
nmi_panic+0x0/0x64 kernel/panic.c:626
mount_root_generic+0x668/0x7a8 init/do_mounts.c:249
mount_block_root init/do_mounts.c:380 [inline]
mount_root+0x198/0x268 init/do_mounts.c:407
prepare_namespace+0xc4/0x2f8 init/do_mounts.c:491
kernel_init_freeable+0x590/0x714 init/main.c:1610
kernel_init+0x24/0x1dc init/main.c:1483
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x082000,04006800,40004000,0400421b
Memory Limit: none
Rebooting in 86400 seconds..


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup