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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <0000000000006e468c06110057ab@google.com>
Date: Fri, 09 Feb 2024 21:30:24 -0800
From: syzbot <syzbot+fbd73dc34f8681ecb8c0@...kaller.appspotmail.com>
To: linux-kernel@...r.kernel.org, linux-next@...r.kernel.org, 
	sfr@...b.auug.org.au, syzkaller-bugs@...glegroups.com
Subject: [syzbot] [kernel?] linux-next boot error: kernel panic: VFS: Unable
 to mount root fs on unknown-block(NUM,NUM) (2)

Hello,

syzbot found the following issue on:

HEAD commit:    ac139fc7db67 Add linux-next specific files for 20240206
git tree:       linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12acdbffe80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2b5fe6166ab1fa63
dashboard link: https://syzkaller.appspot.com/bug?extid=fbd73dc34f8681ecb8c0
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7944e61925e3/disk-ac139fc7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e5fcc1af6c7d/vmlinux-ac139fc7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/be76eb66afdf/bzImage-ac139fc7.xz

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

 (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..


---
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 syzkaller@...glegroups.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