[v6.1] kernel BUG in f2fs_write_inline_data

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 88690811da69 Linux 6.1.92
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17af5314980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ee57a613e7f5bf6c
dashboard link: https://syzkaller.appspot.com/bug?extid=555f80596e7b5d9d8b1d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8b45ba80e02a/disk-88690811.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ca769d644800/vmlinux-88690811.xz
kernel image: https://storage.googleapis.com/syzbot-assets/26a1d8aecbf6/bzImage-88690811.xz

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

F2FS-fs (loop0): Try to recover 1th superblock, ret: 0
F2FS-fs (loop0): Mounted with checkpoint version = 48b305e5
------------[ cut here ]------------
kernel BUG at fs/f2fs/inline.c:259!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 10565 Comm: syz-executor.0 Not tainted 6.1.92-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:f2fs_write_inline_data+0x771/0x780 fs/f2fs/inline.c:259
Code: fd ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c ea fc ff ff 48 89 df e8 9e e8 19 fe e9 dd fc ff ff e8 e4 e3 c2 06 e8 1f 69 c2 fd <0f> 0b e8 18 69 c2 fd 0f 0b 66 0f 1f 44 00 00 55 41 57 41 56 41 55
RSP: 0018:ffffc9000374ee60 EFLAGS: 00010283
RAX: ffffffff83c82431 RBX: 0000000000000001 RCX: 0000000000040000
RDX: ffffc9000b1a9000 RSI: 000000000000cca3 RDI: 000000000000cca4
RBP: ffffc9000374ef90 R08: ffffffff83c81efd R09: ffffed100e27273f
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc9000374eee8
R13: 1ffff1100e27273e R14: ffffc9000374eee0 R15: ffffc9000374eef0
FS: 00007f867180c6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020002000 CR3: 0000000079f6b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
f2fs_write_single_data_page+0xcaf/0x1f90 fs/f2fs/data.c:2841
f2fs_write_cache_pages fs/f2fs/data.c:3143 [inline]
__f2fs_write_data_pages fs/f2fs/data.c:3299 [inline]
f2fs_write_data_pages+0x1ceb/0x3a70 fs/f2fs/data.c:3326
do_writepages+0x3a2/0x670 mm/page-writeback.c:2469
filemap_fdatawrite_wbc+0x121/0x180 mm/filemap.c:388
__filemap_fdatawrite_range mm/filemap.c:421 [inline]
file_write_and_wait_range+0x1ca/0x2b0 mm/filemap.c:774
f2fs_do_sync_file+0x69d/0x1c00 fs/f2fs/file.c:275
generic_write_sync include/linux/fs.h:2957 [inline]
f2fs_file_write_iter+0x720/0x2980 fs/f2fs/file.c:4772
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x7ae/0xba0 fs/read_write.c:584
ksys_write+0x19c/0x2c0 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f8670a7cee9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f867180c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f8670bb3fa0 RCX: 00007f8670a7cee9
RDX: 0000000000002000 RSI: 0000000020000040 RDI: 0000000000000006
RBP: 00007f8670ac947f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f8670bb3fa0 R15: 00007ffecc55d4c8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:f2fs_write_inline_data+0x771/0x780 fs/f2fs/inline.c:259
Code: fd ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c ea fc ff ff 48 89 df e8 9e e8 19 fe e9 dd fc ff ff e8 e4 e3 c2 06 e8 1f 69 c2 fd <0f> 0b e8 18 69 c2 fd 0f 0b 66 0f 1f 44 00 00 55 41 57 41 56 41 55
RSP: 0018:ffffc9000374ee60 EFLAGS: 00010283
RAX: ffffffff83c82431 RBX: 0000000000000001 RCX: 0000000000040000
RDX: ffffc9000b1a9000 RSI: 000000000000cca3 RDI: 000000000000cca4
RBP: ffffc9000374ef90 R08: ffffffff83c81efd R09: ffffed100e27273f
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc9000374eee8
R13: 1ffff1100e27273e R14: ffffc9000374eee0 R15: ffffc9000374eef0
FS: 00007f867180c6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001480534 CR3: 0000000079f6b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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