[v5.15] kernel BUG in ext4_write_inline_data_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1fe619a7d252 Linux 5.15.113
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1405f385280000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab36330fd14820aa
dashboard link: https://syzkaller.appspot.com/bug?extid=23d6388fbebd10b709e4
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14806f51280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16772169280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2d1716ac5a07/disk-1fe619a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9e9e3ef13603/vmlinux-1fe619a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/810a025eede3/bzImage-1fe619a7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/8d6ef50ec44c/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:235!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3733 Comm: syz-executor326 Not tainted 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/25/2023
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:235 [inline]
RIP: 0010:ext4_write_inline_data_end+0x1136/0x11e0 fs/ext4/inline.c:777
Code: 6c 24 08 e9 b8 f9 ff ff e8 c7 74 66 ff 4c 89 ff 48 c7 c6 20 e4 9b 8a e8 38 47 9c ff 0f 0b e8 b1 74 66 ff 0f 0b e8 aa 74 66 ff <0f> 0b e8 a3 74 66 ff eb 2a e8 9c 74 66 ff 49 ff cc 4c 89 24 24 48
RSP: 0018:ffffc900032ff1c0 EFLAGS: 00010293
RAX: ffffffff821974a6 RBX: 000000000000003c RCX: ffff88807e788000
RDX: 0000000000000000 RSI: 000000000000003c RDI: 000000000009c000
RBP: ffffc900032ff2e8 R08: ffffffff8219679a R09: ffffed100f415871
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 000000000009c000 R14: ffff88807a0a8678 R15: ffffea0001c07700
FS: 00007fca81dc4700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 0000000023536000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
generic_perform_write+0x3b7/0x5b0 mm/filemap.c:3787
ext4_buffered_write_iter+0x227/0x360 fs/ext4/file.c:268
ext4_file_write_iter+0x87c/0x1990
do_iter_readv_writev+0x594/0x7a0
do_iter_write+0x1ea/0x760 fs/read_write.c:855
iter_file_splice_write+0x806/0xfa0 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0xe3/0x1c0 fs/splice.c:936
splice_direct_to_actor+0x500/0xc10 fs/splice.c:891
do_splice_direct+0x285/0x3d0 fs/splice.c:979
do_sendfile+0x625/0xff0 fs/read_write.c:1249
__do_sys_sendfile64 fs/read_write.c:1317 [inline]
__se_sys_sendfile64+0x178/0x1e0 fs/read_write.c:1303
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:0x7fca8a9437b9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 c1 18 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fca81dc4208 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00007fca8a9c1798 RCX: 00007fca8a9437b9
RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004
RBP: 00007fca8a9c1790 R08: 00007fca81dc4700 R09: 0000000000000000
R10: 0001000000201005 R11: 0000000000000246 R12: 00007fca8a9c179c
R13: 00007ffcd2179d2f R14: 00007fca81dc4300 R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace 715f9532b262b900 ]---
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:235 [inline]
RIP: 0010:ext4_write_inline_data_end+0x1136/0x11e0 fs/ext4/inline.c:777
Code: 6c 24 08 e9 b8 f9 ff ff e8 c7 74 66 ff 4c 89 ff 48 c7 c6 20 e4 9b 8a e8 38 47 9c ff 0f 0b e8 b1 74 66 ff 0f 0b e8 aa 74 66 ff <0f> 0b e8 a3 74 66 ff eb 2a e8 9c 74 66 ff 49 ff cc 4c 89 24 24 48
RSP: 0018:ffffc900032ff1c0 EFLAGS: 00010293
RAX: ffffffff821974a6 RBX: 000000000000003c RCX: ffff88807e788000
RDX: 0000000000000000 RSI: 000000000000003c RDI: 000000000009c000
RBP: ffffc900032ff2e8 R08: ffffffff8219679a R09: ffffed100f415871
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 000000000009c000 R14: ffff88807a0a8678 R15: ffffea0001c07700
FS: 00007fca81dc4700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000040 CR3: 0000000023536000 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 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 change 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