Hello,
syzbot found the following issue on:
HEAD commit: 6c44e13dc284 Linux 6.1.46
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17f0867fa80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=b2c187b22ae203e6
dashboard link:
https://syzkaller.appspot.com/bug?extid=9310fd5227844fb4dafc
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=10bd6137a80000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=158ff907a80000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/b0d18761f322/disk-6c44e13d.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/13bec23c6ccd/vmlinux-6c44e13d.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/c3754b46d4b8/Image-6c44e13d.gz.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/0fb4b3c79c61/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
[email protected]
F2FS-fs (loop0): Can't find valid F2FS filesystem in 1th superblock
F2FS-fs (loop0): invalid crc value
F2FS-fs (loop0): Found nat_bits in checkpoint
================================================================================
UBSAN: array-index-out-of-bounds in fs/f2fs/f2fs.h:3257:19
index 1409 is out of range for type '__le32[923]' (aka 'unsigned int[923]')
CPU: 1 PID: 4219 Comm: syz-executor128 Not tainted 6.1.46-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_out_of_bounds+0xfc/0x148 lib/ubsan.c:282
inline_data_addr fs/f2fs/f2fs.h:3257 [inline]
__recover_inline_status fs/f2fs/inode.c:111 [inline]
do_read_inode fs/f2fs/inode.c:402 [inline]
f2fs_iget+0x43a0/0x4938 fs/f2fs/inode.c:519
f2fs_fill_super+0x4d88/0x6338 fs/f2fs/super.c:4356
mount_bdev+0x274/0x370 fs/super.c:1432
f2fs_mount+0x44/0x58 fs/f2fs/super.c:4595
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1562
do_new_mount+0x25c/0x8c4 fs/namespace.c:3040
path_mount+0x590/0xe58 fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581
================================================================================
F2FS-fs (loop0): sanity_check_inode: inode (ino=3) is with extra_attr, but extra_attr feature is off
F2FS-fs (loop0): Failed to read root inode
---
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
[email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup