[v6.1] kernel BUG in ext4_write_inline_data

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6ae7ac5c4251 Linux 6.1.130
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1075db8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2d41f94f7752ee8c
dashboard link: https://syzkaller.appspot.com/bug?extid=15d88ef154cc332d3b56
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=179dd074580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e639f43a1070/disk-6ae7ac5c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/eeca5786d4e2/vmlinux-6ae7ac5c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/17f18eb81c7f/Image-6ae7ac5c.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/23f1a49bec2c/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=17b5db8c580000)

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

EXT4-fs (loop0): mounted filesystem without journal. Quota mode: none.
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:236!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4438 Comm: syz.0.17 Not tainted 6.1.130-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236
lr : ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236
sp : ffff8000217e74f0
x29: ffff8000217e7500 x28: 0000000000000078 x27: dfff800000000000
x26: 000000000000003c x25: 0000000000000080 x24: ffff8000217e75c0
x23: ffff0000ea564000 x22: ffff0000ea263a9a x21: ffff0000ea2634d8
x20: 0000000000000008 x19: 0000000000000078 x18: ffff8000217e7100
x17: ffff800018c58000 x16: ffff8000122e0990 x15: 0000000000000000
x14: 00000000ffffffc3 x13: ffff0000d881b780 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008e3a9ec
x8 : ffff0000d881b780 x7 : ffff800008ddf598 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000078 x3 : 0000000000000008
x2 : ffff0000ea564000 x1 : 000000000000003c x0 : 0000000000000080
Call trace:
ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236
ext4_write_inline_data_end+0x300/0xc94 fs/ext4/inline.c:777
ext4_da_write_end+0x414/0x940 fs/ext4/inode.c:3091
generic_perform_write+0x384/0x55c mm/filemap.c:3856
ext4_buffered_write_iter+0x2e0/0x538 fs/ext4/file.c:285
ext4_file_write_iter+0x18c/0x1654
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x91c fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: 17ffffcb 97dae47c d4210000 97dae47a (d4210000)
---[ end trace 0000000000000000 ]---


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: 8e60a714ba3b Linux 6.1.132
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=101463e4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14036d226c9c97a0

dashboard link: https://syzkaller.appspot.com/bug?extid=15d88ef154cc332d3b56
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c1c7b0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=126ec998580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/015af6f03147/disk-8e60a714.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4dd00fc87c24/vmlinux-8e60a714.xz
kernel image: https://storage.googleapis.com/syzbot-assets/318920d71f18/Image-8e60a714.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9145c3998b41/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16448e78580000)

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

------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:236!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4579 Comm: syz-executor237 Not tainted 6.1.132-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236
lr : ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236

sp : ffff8000219374f0
x29: ffff800021937500 x28: 0000000000000078 x27: dfff800000000000
x26: 000000000000003c x25: 0000000000000080 x24: ffff8000219375c0
x23: ffff0000e396e000 x22: ffff0000df1758b2 x21: ffff0000df1752f0
x20: 0000000000000008 x19: 0000000000000078 x18: 1fffe0003679c776
x17: ffff800015afd000 x16: ffff8000122de87c x15: 0000000000000000
x14: 00000000ffffffc3 x13: ffff0000d8110000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff800008e399b8
x8 : ffff0000d8110000 x7 : ffff800008dde564 x6 : 0000000000000000

x5 : 0000000000000000 x4 : 0000000000000078 x3 : 0000000000000008

x2 : ffff0000e396e000 x1 : 000000000000003c x0 : 0000000000000080

Call trace:
ext4_write_inline_data+0x2fc/0x300 fs/ext4/inline.c:236
ext4_write_inline_data_end+0x300/0xc94 fs/ext4/inline.c:777
ext4_da_write_end+0x414/0x940 fs/ext4/inode.c:3091
generic_perform_write+0x384/0x55c mm/filemap.c:3856
ext4_buffered_write_iter+0x2e0/0x538 fs/ext4/file.c:285

ext4_file_write_iter+0x18c/0x1654 fs/ext4/file.c:-1

call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x91c fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Code: 17ffffcb 97dae8cd d4210000 97dae8cb (d4210000)

---[ end trace 0000000000000000 ]---


---