[f2fs?] [tmpfs?] kernel BUG in f2fs_evict_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c4215ee4771b Linux 4.14.302
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1475ae54480000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a9988fe055c9527
dashboard link: https://syzkaller.appspot.com/bug?extid=a0d4ec347cb46afbc0ef
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156871a8480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=123eb560480000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c93ba055d204/disk-c4215ee4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bfbc929a33c1/vmlinux-c4215ee4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/444658051770/bzImage-c4215ee4.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f5f8c91bfe14/mount_0.gz

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

F2FS-fs (loop0): Try to recover 2th superblock, ret: -30
F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4
F2FS-fs (loop0): Corrupted max_depth of 3: 2049
syz-executor289[7985]: segfault at 0 ip 00007f14a3e7aac0 sp 00007ffc57154f18 error 4 in syz-executor2894277320[7f14a3e14000+88000]
------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:600!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 7985 Comm: syz-executor289 Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880b4410540 task.stack: ffff8880b3008000
RIP: 0010:f2fs_evict_inode+0xd97/0x1070 fs/f2fs/inode.c:600
RSP: 0018:ffff8880b300f858 EFLAGS: 00010297
RAX: ffff8880b4410540 RBX: ffff8880b3788340 RCX: 0000000000000001
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8880b37883c4
RBP: ffff88808e3a2000 R08: 0000000000000003 R09: 0000000000000001
R10: 0000000000000000 R11: ffff8880b4410540 R12: ffff888096e78ac0
R13: ffff88808e3a2028 R14: ffff88808e3a23d0 R15: ffff88808e3a21b8
FS: 0000555555746300(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff373823000 CR3: 00000000a1249000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
evict+0x2c8/0x700 fs/inode.c:554
dispose_list+0x109/0x1e0 fs/inode.c:589
evict_inodes+0x2cd/0x3a0 fs/inode.c:639
generic_shutdown_super+0xb3/0x370 fs/super.c:438
kill_block_super+0x95/0xe0 fs/super.c:1161
deactivate_locked_super+0x6c/0xd0 fs/super.c:319
deactivate_super+0x7f/0xa0 fs/super.c:350
cleanup_mnt+0x186/0x2c0 fs/namespace.c:1183
task_work_run+0x11f/0x190 kernel/task_work.c:113
exit_task_work include/linux/task_work.h:22 [inline]
do_exit+0xa44/0x2850 kernel/exit.c:868
do_group_exit+0x100/0x2e0 kernel/exit.c:965
get_signal+0x38d/0x1ca0 kernel/signal.c:2412
do_signal+0x7c/0x1550 arch/x86/kernel/signal.c:792
exit_to_usermode_loop+0x160/0x200 arch/x86/entry/common.c:160
prepare_exit_to_usermode+0x1af/0x210 arch/x86/entry/common.c:199
retint_user+0x8/0x18
RIP: 0033:0x7f14a3e7aac0
RSP: 002b:00007ffc57154f18 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00000000000000e0 RCX: 0000000000000000
RDX: 00000000000000e0 RSI: 00000000000000e0 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 00000000000000c0 R11: 00000000000000e0 R12: 0000000020000100
R13: 00007ffc57154fe0 R14: 0000000000000000 R15: 00007ffc57154fe0
Code: 92 fe 48 c7 c2 e0 be c1 87 be 18 01 00 00 48 c7 c7 40 bf c1 87 c6 05 b1 02 30 07 01 e8 4c 68 3f 04 e9 35 fc ff ff e8 e9 0c 92 fe <0f> 0b 48 8b 7c 24 28 e8 6d cd bb fe e9 ec f2 ff ff e8 63 cd bb
RIP: f2fs_evict_inode+0xd97/0x1070 fs/f2fs/inode.c:600 RSP: ffff8880b300f858
---[ end trace dc0d59a735f28234 ]---


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches