linux-kernel - [syzbot] [kernel?] upstream-arm64 test error: kernel panic: VFS: Unable to mount root fs on unknown-block(NUM,NUM)

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <0000000000001fcd17062139be6d@google.com>
Date: Tue, 03 Sep 2024 09:42:26 -0700
From: syzbot <syzbot+3d91bb43ea9bd71b490e@...kaller.appspotmail.com>
To: catalin.marinas@....com, linux-arm-kernel@...ts.infradead.org, 
	linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com, 
	will@...nel.org
Subject: [syzbot] [kernel?] upstream-arm64 test error: kernel panic: VFS:
 Unable to mount root fs on unknown-block(NUM,NUM)

Hello,

syzbot found the following issue on:

HEAD commit:    8efd4bbd16de Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=17016cfb980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e8ce0989a72ac4ae
dashboard link: https://syzkaller.appspot.com/bug?extid=3d91bb43ea9bd71b490e
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/915e34fff8d7/disk-8efd4bbd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/630f1f097016/vmlinux-8efd4bbd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1f1385be55d6/Image-8efd4bbd.gz.xz

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

 (driver?)
  103:00001     262144 nvme0n1p1 fb1dbdda-6850-4ddd-ad86-b1774de646a7

  103:00002    1048576 nvme0n1p2 d730f21b-d9a9-4cec-9f43-3402be542af1

1f00             128 mtdblock0 
 (driver?)
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(0,0)
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc5-syzkaller-g8efd4bbd16de #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Call trace:
 dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:317
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:324
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:119
 dump_stack+0x1c/0x28 lib/dump_stack.c:128
 panic+0x300/0x884 kernel/panic.c:354
 mount_root_generic+0x4c4/0x5b8 init/do_mounts.c:236
 mount_block_root+0x6c/0x7c init/do_mounts.c:380
 mount_root+0xb4/0xe4 init/do_mounts.c:407
 prepare_namespace+0xdc/0x11c init/do_mounts.c:491
 kernel_init_freeable+0x360/0x478 init/main.c:1591
 kernel_init+0x24/0x2a0 init/main.c:1467
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x08,00000103,80100128,42017203
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 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