syzbot has found a reproducer for the following issue on:
HEAD commit: 80529b4968a8 Linux 5.15.138
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=144140bf680000
kernel config:
https://syzkaller.appspot.com/x/.config?x=c431dbb457f792c5
syz repro:
https://syzkaller.appspot.com/x/repro.syz?x=11fb3720e80000
C reproducer:
https://syzkaller.appspot.com/x/repro.c?x=12f064f0e80000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/4fd4b10a6041/disk-80529b49.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/60443f81279e/vmlinux-80529b49.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/c7f38af1be13/bzImage-80529b49.xz
mounted in repro:
https://storage.googleapis.com/syzbot-assets/79aae97bf142/mount_0.gz
F2FS-fs (loop0): Found nat_bits in checkpoint
F2FS-fs (loop0): recover fsync data on readonly fs
F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4
F2FS-fs (loop0): Corrupted max_depth of 3: 16777217
------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:833!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3499 Comm: syz-executor595 Not tainted 5.15.138-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
RIP: 0010:f2fs_evict_inode+0x14ec/0x1510 fs/f2fs/inode.c:833
Code: de e8 58 14 eb fd 31 ff 89 de e8 4f 14 eb fd 40 84 ed 75 24 e8 e5 11 eb fd e9 25 ec ff ff e8 db 11 eb fd 0f 0b e8 d4 11 eb fd <0f> 0b e8 cd 11 eb fd 0f 0b e9 02 ff ff ff e8 c1 11 eb fd e8 e4 76
RSP: 0018:ffffc90002bff930 EFLAGS: 00010293
RAX: ffffffff8395107c RBX: 0000000000000002 RCX: ffff888013385940
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff839503b5 R09: ffffed100e9132f7
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807a134000
R13: ffff888074899300 R14: 1ffff1100e9132f6 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005645e8c57218 CR3: 000000007f5c4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
evict+0x2a4/0x620 fs/inode.c:587
dispose_list fs/inode.c:620 [inline]
evict_inodes+0x601/0x6a0 fs/inode.c:670
generic_shutdown_super+0x99/0x2c0 fs/super.c:454
kill_block_super+0x7a/0xe0 fs/super.c:1414
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4501
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0x6a3/0x2480 kernel/exit.c:872
do_group_exit+0x144/0x310 kernel/exit.c:994
__do_sys_exit_group kernel/exit.c:1005 [inline]
__se_sys_exit_group kernel/exit.c:1003 [inline]
__x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1003
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fb7ed43e749
Code: Unable to access opcode bytes at RIP 0x7fb7ed43e71f.
RSP: 002b:00007fff7f2b3058 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007fb7ed43e749
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 00007fb7ed4bf2b0 R08: ffffffffffffffb8 R09: 00007fff7f2b3130
R10: 00007fff7f2b2f80 R11: 0000000000000246 R12: 00007fb7ed4bf2b0
R13: 0000000000000000 R14: 00007fb7ed4c0020 R15: 00007fb7ed40cc90
</TASK>
Modules linked in:
---[ end trace 258a1d28484a3cc0 ]---
RIP: 0010:f2fs_evict_inode+0x14ec/0x1510 fs/f2fs/inode.c:833
Code: de e8 58 14 eb fd 31 ff 89 de e8 4f 14 eb fd 40 84 ed 75 24 e8 e5 11 eb fd e9 25 ec ff ff e8 db 11 eb fd 0f 0b e8 d4 11 eb fd <0f> 0b e8 cd 11 eb fd 0f 0b e9 02 ff ff ff e8 c1 11 eb fd e8 e4 76
RSP: 0018:ffffc90002bff930 EFLAGS: 00010293
RAX: ffffffff8395107c RBX: 0000000000000002 RCX: ffff888013385940
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff839503b5 R09: ffffed100e9132f7
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807a134000
R13: ffff888074899300 R14: 1ffff1100e9132f6 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005645e8c57218 CR3: 000000007f5c4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.