kernel BUG in ext4_write_inline_data_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4305285a3554 Merge 5.15.71 into android13-5.15-lts
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=163ae95c880000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd3918ed313a2351
dashboard link: https://syzkaller.appspot.com/bug?extid=8234f4fea762dd893f3d
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155ff748880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=129fa914880000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5c9a177611b7/disk-4305285a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/54b99d9e067b/vmlinux-4305285a.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/ae8f76cfc888/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:227!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 446 Comm: syz-executor355 Not tainted 5.15.71-syzkaller-04238-g4305285a3554 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:227 [inline]
RIP: 0010:ext4_write_inline_data_end+0xdeb/0xdf0 fs/ext4/inline.c:782
Code: f7 e8 b9 1e cd ff e9 1b fa ff ff e8 6f 77 cf 02 e8 8a 93 8f ff 0f 0b e8 83 93 8f ff 0f 0b e8 7c 93 8f ff 0f 0b e8 75 93 8f ff <0f> 0b 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0
RSP: 0018:ffffc90000c67040 EFLAGS: 00010293
RAX: ffffffff81e0ae4b RBX: 0000000000000048 RCX: ffff88810b420000
RDX: 0000000000000000 RSI: 0000000000000048 RDI: 000000000000ed8d
RBP: ffffc90000c67190 R08: ffffffff81e0a451 R09: ffffed1022dc904b
R10: ffffed1022dc904b R11: 1ffff11022dc904a R12: 000000000000ed8d
R13: dffffc0000000000 R14: 000000000000ed84 R15: 0000000000000009
FS: 00005555572b7300(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007febd6631290 CR3: 000000010ebfc000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_write_end+0x1c4/0xcf0 fs/ext4/inode.c:1307
ext4_da_write_end+0x92/0xa40 fs/ext4/inode.c:3067
generic_perform_write+0x3c7/0x5d0 mm/filemap.c:3836
ext4_buffered_write_iter+0x49b/0x630 fs/ext4/file.c:271
ext4_file_write_iter+0x449/0x1bc0
do_iter_readv_writev+0x52a/0x720
do_iter_write+0x1f4/0x760 fs/read_write.c:855
vfs_iter_write+0x7c/0xa0 fs/read_write.c:896
iter_file_splice_write+0x810/0xfd0 fs/splice.c:689
do_splice_from fs/splice.c:767 [inline]
direct_splice_actor+0xfe/0x130 fs/splice.c:934
splice_direct_to_actor+0x4d4/0xbd0 fs/splice.c:889
do_splice_direct+0x2a0/0x3f0 fs/splice.c:977
do_sendfile+0x63b/0xfd0 fs/read_write.c:1249
__do_sys_sendfile64 fs/read_write.c:1317 [inline]
__se_sys_sendfile64 fs/read_write.c:1303 [inline]
__x64_sys_sendfile64+0x1ce/0x230 fs/read_write.c:1303
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x44/0xd0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7febd65bb5b9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffe3ab40b38 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 00000000000053ab RCX: 00007febd65bb5b9
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000003
RBP: 0000000000000000 R08: 00007ffe3ab40b60 R09: 00007ffe3ab40b60
R10: 0000000000010000 R11: 0000000000000246 R12: 00007ffe3ab40b5c
R13: 00007ffe3ab40b90 R14: 00007ffe3ab40b70 R15: 0000000000000003
</TASK>
Modules linked in:
---[ end trace a91821d3488c996e ]---
RIP: 0010:ext4_write_inline_data fs/ext4/inline.c:227 [inline]
RIP: 0010:ext4_write_inline_data_end+0xdeb/0xdf0 fs/ext4/inline.c:782
Code: f7 e8 b9 1e cd ff e9 1b fa ff ff e8 6f 77 cf 02 e8 8a 93 8f ff 0f 0b e8 83 93 8f ff 0f 0b e8 7c 93 8f ff 0f 0b e8 75 93 8f ff <0f> 0b 0f 1f 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 e4 e0
RSP: 0018:ffffc90000c67040 EFLAGS: 00010293
RAX: ffffffff81e0ae4b RBX: 0000000000000048 RCX: ffff88810b420000
RDX: 0000000000000000 RSI: 0000000000000048 RDI: 000000000000ed8d
RBP: ffffc90000c67190 R08: ffffffff81e0a451 R09: ffffed1022dc904b
R10: ffffed1022dc904b R11: 1ffff11022dc904a R12: 000000000000ed8d
R13: dffffc0000000000 R14: 000000000000ed84 R15: 0000000000000009
FS: 00005555572b7300(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007febd6631290 CR3: 000000010ebfc000 CR4: 00000000003506b0
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches