[Android 5.10] kernel BUG in ext4_create_inline_data

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cf6ed0f1511d Merge android13-5.10 into android13-5.10-lts
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=165a2c82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=60d050dca46c7aa2
dashboard link: https://syzkaller.appspot.com/bug?extid=f71143daec353905de1a
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157c680c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137c680c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5e615cc034ea/disk-cf6ed0f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8b123186e0aa/vmlinux-cf6ed0f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/bb508f5309d6/bzImage-cf6ed0f1.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/2ceb8f60ba15/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=122181d4580000)

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

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:300!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 282 Comm: syz-executor396 Not tainted 5.10.237-syzkaller-00010-gcf6ed0f1511d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ext4_create_inline_data+0x40a/0x410 fs/ext4/inline.c:300
Code: ff ff e8 d9 3f d0 ff e9 11 ff ff ff 89 f9 80 e1 07 fe c1 38 c1 0f 8c 2f ff ff ff e8 c0 3f d0 ff e9 25 ff ff ff e8 96 4f 96 ff <0f> 0b 0f 1f 40 00 55 48 89 e5 41 57 41 56 53 48 89 fb e8 7f 4f 96
RSP: 0018:ffffc90000b972e0 EFLAGS: 00010293
RAX: ffffffff81cd42da RBX: ffff88811c3eebe8 RCX: ffff888104bd8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b97410 R08: 0000000000000000 R09: ffffed102387dd55
R10: ffffed102387dd55 R11: 1ffff1102387dd54 R12: 0000000000000000
R13: 1ffff92000172e60 R14: 0000000000000000 R15: ffff88811c3eebe8
FS: 000055558de4b380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000e40 CR3: 000000012183c000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_prepare_inline_data+0x16a/0x1f0 fs/ext4/inline.c:410
ext4_try_to_write_inline_data+0x30c/0x1140 fs/ext4/inline.c:700
ext4_write_begin+0x219/0x1550 fs/ext4/inode.c:1192
generic_perform_write+0x2be/0x510 mm/filemap.c:3509
ext4_buffered_write_iter+0x4b8/0x640 fs/ext4/file.c:271
ext4_file_write_iter+0x536/0x1980 fs/ext4/file.c:-1
call_write_iter include/linux/fs.h:2058 [inline]
new_sync_write fs/read_write.c:518 [inline]
vfs_write+0x725/0xd60 fs/read_write.c:605
ksys_write+0x140/0x240 fs/read_write.c:658
__do_sys_write fs/read_write.c:670 [inline]
__se_sys_write fs/read_write.c:667 [inline]
__x64_sys_write+0x7b/0x90 fs/read_write.c:667
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7fac42c6d879
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 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:00007fffd17445f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fffd17447d8 RCX: 00007fac42c6d879
RDX: 0000000000000009 RSI: 00002000000000c0 RDI: 0000000000000004
RBP: 00007fac42ce0610 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fffd17447c8 R14: 0000000000000001 R15: 0000000000000001
Modules linked in:
---[ end trace f8b87a196e3f560d ]---
RIP: 0010:ext4_create_inline_data+0x40a/0x410 fs/ext4/inline.c:300
Code: ff ff e8 d9 3f d0 ff e9 11 ff ff ff 89 f9 80 e1 07 fe c1 38 c1 0f 8c 2f ff ff ff e8 c0 3f d0 ff e9 25 ff ff ff e8 96 4f 96 ff <0f> 0b 0f 1f 40 00 55 48 89 e5 41 57 41 56 53 48 89 fb e8 7f 4f 96
RSP: 0018:ffffc90000b972e0 EFLAGS: 00010293
RAX: ffffffff81cd42da RBX: ffff88811c3eebe8 RCX: ffff888104bd8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90000b97410 R08: 0000000000000000 R09: ffffed102387dd55
R10: ffffed102387dd55 R11: 1ffff1102387dd54 R12: 0000000000000000
R13: 1ffff92000172e60 R14: 0000000000000000 R15: ffff88811c3eebe8
FS: 000055558de4b380(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000e40 CR3: 000000012183c000 CR4: 00000000003506a0
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