syzbot


linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM) (2)

Status: auto-obsoleted due to no activity on 2024/04/06 14:44
Subsystems: kernel
[Documentation on labels]
Reported-by: syzbot+fbd73dc34f8681ecb8c0@syzkaller.appspotmail.com
First crash: 70d, last: 70d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [kernel?] linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM) (2) 0 (1) 2024/02/10 05:30
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM) kernel 332 712d 714d 0/26 auto-closed as invalid on 2022/06/14 10:41

Sample crash report:
 (driver?)
1f00             128 mtdblock0 
 (driver?)
0800         2097152 sda 
 driver: sd
  0801         1048576 sda1 00000000-01

List of all bdev filesystems:
 reiserfs
 ext3
 ext2
 ext4
 cramfs
 squashfs
 minix
 vfat
 msdos
 exfat
 bfs
 iso9660
 hfsplus
 hfs
 vxfs
 sysv
 v7
 hpfs
 ntfs3
 ufs
 efs
 affs
 romfs
 qnx4
 qnx6
 adfs
 fuseblk
 udf
 omfs
 jfs
 xfs
 nilfs2
 befs
 ocfs2
 gfs2
 gfs2meta
 f2fs
 bcachefs
 erofs
 zonefs
 btrfs

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.8.0-rc3-next-20240206-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
 panic+0x349/0x860 kernel/panic.c:348
 mount_root_generic+0x3b5/0x3e0 init/do_mounts.c:234
 prepare_namespace+0xc2/0x100 init/do_mounts.c:489
 kernel_init_freeable+0x471/0x5d0 init/main.c:1555
 kernel_init+0x1d/0x2b0 init/main.c:1432
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:242
 </TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/06 14:43 linux-next ac139fc7db67 6404acf9 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
2024/02/06 14:43 linux-next ac139fc7db67 6404acf9 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
2024/02/06 14:43 linux-next ac139fc7db67 6404acf9 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
2024/02/06 05:19 linux-next ac139fc7db67 4e988e80 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
2024/02/06 05:19 linux-next ac139fc7db67 4e988e80 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
2024/02/06 05:19 linux-next ac139fc7db67 4e988e80 .config console log report [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root linux-next boot error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)
* Struck through repros no longer work on HEAD.