[Android 6.1] kernel BUG in ext4_write_inline_data_end

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: a59b32866cd4 UPSTREAM: usb: gadget: udc: Handle gadget_con..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=10bf2ca7680000
kernel config: https://syzkaller.appspot.com/x/.config?x=e9500dd6486f6367
dashboard link: https://syzkaller.appspot.com/bug?extid=8116d2c9a7677fd7d3f3
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141a7338e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1047c0b8e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a0a1be7cafd2/disk-a59b3286.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/91d6626c1eb5/vmlinux-a59b3286.xz
kernel image: https://storage.googleapis.com/syzbot-assets/92a8c4773913/bzImage-a59b3286.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/80cfaf4b8e2c/mount_0.gz

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

EXT4-fs error (device loop0): __ext4_fill_super:5386: inode #2: comm syz-executor848: casefold flag without casefold feature
EXT4-fs (loop0): warning: mounting fs with errors, running e2fsck is recommended
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:767!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 1202 Comm: syz-executor848 Not tainted 6.1.43-syzkaller-00009-ga59b32866cd4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
RIP: 0010:ext4_write_inline_data_end+0xa85/0xa90 fs/ext4/inline.c:767
Code: f8 ff ff 44 89 e9 80 e1 07 fe c1 38 c1 0f 8c 17 fb ff ff 4c 89 ef e8 7a 0d cb ff e9 0a fb ff ff e8 a0 29 05 03 e8 bb 84 84 ff <0f> 0b e8 b4 84 84 ff 0f 0b 66 90 55 48 89 e5 41 57 41 56 41 55 41
RSP: 0018:ffffc90001aa76e0 EFLAGS: 00010293
RAX: ffffffff81f07815 RBX: 0000000000000000 RCX: ffff888112772880
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90001aa77f8 R08: ffffffff81f07003 R09: ffffed10200b0b7b
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000004c00000000
R13: ffff888112772880 R14: ffff888100585bd0 R15: ffff888100585ce8
FS: 00007f2089ece6c0(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200001a0 CR3: 000000011972d000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_write_end+0x395/0x910 fs/ext4/inode.c:1311
ext4_da_write_end+0x88/0x9a0 fs/ext4/inode.c:3061
generic_perform_write+0x3e6/0x5c0 mm/filemap.c:3785
ext4_buffered_write_iter+0x360/0x640 fs/ext4/file.c:285
ext4_file_write_iter+0x194/0x1cf0
call_write_iter include/linux/fs.h:2215 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x902/0xeb0 fs/read_write.c:584
ksys_write+0x199/0x2c0 fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:646
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+0x63/0xcd
RIP: 0033:0x7f2089f11ed9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 b1 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2089ece218 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f2089f9a6c8 RCX: 00007f2089f11ed9
RDX: 0000000000000007 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 0000000000000018 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f2089f9a6c0
R13: 00007f2089f98100 R14: 00007f2089f66650 R15: 00007f2089f6606b
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_write_inline_data_end+0xa85/0xa90 fs/ext4/inline.c:767
Code: f8 ff ff 44 89 e9 80 e1 07 fe c1 38 c1 0f 8c 17 fb ff ff 4c 89 ef e8 7a 0d cb ff e9 0a fb ff ff e8 a0 29 05 03 e8 bb 84 84 ff <0f> 0b e8 b4 84 84 ff 0f 0b 66 90 55 48 89 e5 41 57 41 56 41 55 41
RSP: 0018:ffffc90001aa76e0 EFLAGS: 00010293
RAX: ffffffff81f07815 RBX: 0000000000000000 RCX: ffff888112772880
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90001aa77f8 R08: ffffffff81f07003 R09: ffffed10200b0b7b
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000004c00000000
R13: ffff888112772880 R14: ffff888100585bd0 R15: ffff888100585ce8
FS: 00007f2089ece6c0(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000180 CR3: 000000011972d000 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.

If the report is already addressed, 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 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