[Android 5.15] kernel BUG in ext4_es_cache_extent

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 13d6d33696ef Merge 5.15.200 into android13-5.15-lts
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=11e84152580000
kernel config: https://syzkaller.appspot.com/x/.config?x=deffac0a782f1cb0
dashboard link: https://syzkaller.appspot.com/bug?extid=bd36204ef9201acb1b1e
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1206d722580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15948006580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/49c205e65f10/disk-13d6d336.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e3df4a3942b9/vmlinux-13d6d336.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ac1426590472/bzImage-13d6d336.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e5c2ce9f9fbb/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=148cd95a580000)

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

------------[ cut here ]------------
kernel BUG at fs/ext4/extents_status.c:968!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 45 Comm: kworker/u4:2 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Workqueue: ext4-rsv-conversion ext4_end_io_rsv_work
RIP: 0010:ext4_es_cache_extent+0x57b/0x5d0 fs/ext4/extents_status.c:968
Code: e8 03 42 80 3c 38 00 74 08 48 89 df e8 0e 51 d2 ff 48 8b 3b 48 8b 74 24 28 48 8d 54 24 60 e8 8c da 0c 00 eb 13 e8 85 22 93 ff <0f> 0b e8 7e 22 93 ff eb 28 e8 77 22 93 ff 31 f6 65 ff 0d f6 c2 2b
RSP: 0018:ffffc900002ef4c0 EFLAGS: 00010293
RAX: ffffffff81d6aa7b RBX: 0000000000000010 RCX: ffff8881055f62c0
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 000000000000000e
RBP: ffffc900002ef5e0 R08: ffffc900002ef537 R09: ffffc900002ef520
R10: dffffc0000000000 R11: fffff5200005dea7 R12: ffff88811110c3c8
R13: 47ffffffffffffff R14: 000000000000000e R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000016000 CR3: 000000010d56e000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_cache_extents fs/ext4/extents.c:517 [inline]
ext4_find_extent+0x508/0xe20 fs/ext4/extents.c:918
ext4_ext_map_blocks+0x207/0x61e0 fs/ext4/extents.c:4166
ext4_map_blocks+0x988/0x1b30 fs/ext4/inode.c:674
ext4_convert_unwritten_extents+0x2b7/0x5f0 fs/ext4/extents.c:4869
ext4_convert_unwritten_io_end_vec+0x103/0x180 fs/ext4/extents.c:4908
ext4_end_io_end fs/ext4/page-io.c:186 [inline]
ext4_do_flush_completed_IO fs/ext4/page-io.c:259 [inline]
ext4_end_io_rsv_work+0x2c1/0x610 fs/ext4/page-io.c:273
process_one_work+0x6be/0xba0 kernel/workqueue.c:2325
worker_thread+0xa59/0x1200 kernel/workqueue.c:2472
kthread+0x411/0x500 kernel/kthread.c:337
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Modules linked in:
---[ end trace d988c7fe758d0df8 ]---
RIP: 0010:ext4_es_cache_extent+0x57b/0x5d0 fs/ext4/extents_status.c:968
Code: e8 03 42 80 3c 38 00 74 08 48 89 df e8 0e 51 d2 ff 48 8b 3b 48 8b 74 24 28 48 8d 54 24 60 e8 8c da 0c 00 eb 13 e8 85 22 93 ff <0f> 0b e8 7e 22 93 ff eb 28 e8 77 22 93 ff 31 f6 65 ff 0d f6 c2 2b
RSP: 0018:ffffc900002ef4c0 EFLAGS: 00010293
RAX: ffffffff81d6aa7b RBX: 0000000000000010 RCX: ffff8881055f62c0
RDX: 0000000000000000 RSI: 0000000000000010 RDI: 000000000000000e
RBP: ffffc900002ef5e0 R08: ffffc900002ef537 R09: ffffc900002ef520
R10: dffffc0000000000 R11: fffff5200005dea7 R12: ffff88811110c3c8
R13: 47ffffffffffffff R14: 000000000000000e R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000016000 CR3: 000000011f5d2000 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