[v6.6] kernel BUG in f2fs_evict_inode

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: bb9c90ab9c5a Linux 6.6.102
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10fc16f0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b989b97a0687b0a
dashboard link: https://syzkaller.appspot.com/bug?extid=23e5acd67ef844cb0e33
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/44e2224124c3/disk-bb9c90ab.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/33e0aef7ff42/vmlinux-bb9c90ab.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0515bc436228/bzImage-bb9c90ab.xz

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

------------[ cut here ]------------
kernel BUG at fs/f2fs/inode.c:936!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 10597 Comm: syz-executor Not tainted 6.6.102-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:f2fs_evict_inode+0x17e3/0x1800 fs/f2fs/inode.c:936
Code: c5 40 0f 94 c6 bf 02 00 00 00 e8 b8 ed d9 fd 40 84 ed 75 24 e8 1e eb d9 fd e9 1b ea ff ff e8 14 eb d9 fd 0f 0b e8 0d eb d9 fd <0f> 0b e8 06 eb d9 fd 0f 0b e9 04 ff ff ff e8 fa ea d9 fd e8 f5 fb
RSP: 0018:ffffc90003297948 EFLAGS: 00010293
RAX: ffffffff83aba013 RBX: ffff8880485811b0 RCX: ffff8880298a3c00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 1ffff110090b0240 R08: ffff888048581667 R09: 1ffff110090b02cc
R10: dffffc0000000000 R11: ffffed10090b02cd R12: ffff888024d22084
R13: 1ffff110090b02cc R14: 0000000000000002 R15: ffff888048581660
FS: 000055557514d500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffe418afff8 CR3: 000000007afa5000 CR4: 00000000003506e0
Call Trace:
<TASK>
evict+0x486/0x870 fs/inode.c:705
dispose_list fs/inode.c:738 [inline]
evict_inodes+0x5fe/0x690 fs/inode.c:792
generic_shutdown_super+0x97/0x2b0 fs/super.c:672
kill_block_super+0x44/0x90 fs/super.c:1660
kill_f2fs_super+0x30a/0x3c0 fs/f2fs/super.c:4887
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0c5f58ff17
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe418b0288 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f0c5f611c05 RCX: 00007f0c5f58ff17
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe418b0340
RBP: 00007ffe418b0340 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe418b13d0
R13: 00007f0c5f611c05 R14: 00000000000b54eb R15: 00007ffe418b1410
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:f2fs_evict_inode+0x17e3/0x1800 fs/f2fs/inode.c:936
Code: c5 40 0f 94 c6 bf 02 00 00 00 e8 b8 ed d9 fd 40 84 ed 75 24 e8 1e eb d9 fd e9 1b ea ff ff e8 14 eb d9 fd 0f 0b e8 0d eb d9 fd <0f> 0b e8 06 eb d9 fd 0f 0b e9 04 ff ff ff e8 fa ea d9 fd e8 f5 fb
RSP: 0018:ffffc90003297948 EFLAGS: 00010293
RAX: ffffffff83aba013 RBX: ffff8880485811b0 RCX: ffff8880298a3c00
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 1ffff110090b0240 R08: ffff888048581667 R09: 1ffff110090b02cc
R10: dffffc0000000000 R11: ffffed10090b02cd R12: ffff888024d22084
R13: 1ffff110090b02cc R14: 0000000000000002 R15: ffff888048581660
FS: 000055557514d500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2eb1784198 CR3: 000000007afa5000 CR4: 00000000003506e0


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

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.