[Android 5.10] kernel BUG in ext4_es_cache_extent (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 2ece552169c2 Revert "genirq: Export affinity setter for mo..
git tree: android13-5.10-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=16e7552f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5193c33e6e6dcf8b
dashboard link: https://syzkaller.appspot.com/bug?extid=535e2f1ec9d23e031cd4
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d0ec58580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137de5e2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/920655e06ee9/disk-2ece5521.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/c675d5ecc06e/vmlinux-2ece5521.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d011a1539812/bzImage-2ece5521.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/9207f3d5d318/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=167e0734580000)

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

EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
EXT4-fs (loop2): encrypted files will use data=ordered instead of data journaling mode
EXT4-fs (loop2): 1 truncate cleaned up
EXT4-fs (loop2): mounted filesystem without journal. Opts: i_version,nombcache,debug_want_extra_isize=0x0000000000000068,lazytime,block_validity,bsddf,init_itable=0x0000000000000010,debug_want_extra_isize=0x000000000000000c,,errors=continue
------------[ cut here ]------------
kernel BUG at fs/ext4/extents_status.c:205!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 378 Comm: syz.2.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:ext4_es_end fs/ext4/extents_status.c:205 [inline]
RIP: 0010:__es_tree_search fs/ext4/extents_status.c:223 [inline]
RIP: 0010:ext4_es_cache_extent+0x4d6/0x5d0 fs/ext4/extents_status.c:972
Code: d2 ff e9 15 ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 8f fe ff ff 4c 89 f7 e8 84 ed d2 ff e9 82 fe ff ff e8 da fd 98 ff <0f> 0b 49 89 de 65 8b 05 7e 69 37 7e 89 c3 c1 e8 06 48 8d 3c c5 68
RSP: 0018:ffffc90000ec74c0 EFLAGS: 00010293
RAX: ffffffff81caa7c6 RBX: 0000000000000000 RCX: ffff88810f95e2c0
RDX: 0000000000000000 RSI: 000000000f95eb42 RDI: 0000000000000000
RBP: ffffc90000ec75e0 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001d8e88 R11: 1ffff920001d8e88 R12: 000000000f95eb42
R13: 1ffff11024b82a11 R14: ffff888125c1508c R15: dffffc0000000000
FS: 000055556be89500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32a63fff CR3: 000000010f597000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_cache_extents fs/ext4/extents.c:521 [inline]
ext4_find_extent+0x59d/0xe20 fs/ext4/extents.c:917
ext4_get_verity_descriptor_location fs/ext4/verity.c:296 [inline]
ext4_get_verity_descriptor+0x107/0x500 fs/ext4/verity.c:352
fsverity_get_descriptor+0x8e/0x460 fs/verity/open.c:273
ensure_verity_info fs/verity/open.c:315 [inline]
fsverity_file_open+0x11f/0x230 fs/verity/open.c:356
ext4_file_open+0x220/0x600 fs/ext4/file.c:861
do_dentry_open+0x793/0x1090 fs/open.c:819
vfs_open+0x73/0x80 fs/open.c:942
do_open fs/namei.c:3391 [inline]
path_openat+0x27ad/0x3160 fs/namei.c:3509
do_filp_open+0x1b3/0x3e0 fs/namei.c:3536
do_sys_openat2+0x14c/0x6d0 fs/open.c:1217
do_sys_open fs/open.c:1233 [inline]
__do_sys_openat fs/open.c:1249 [inline]
__se_sys_openat fs/open.c:1244 [inline]
__x64_sys_openat+0x136/0x160 fs/open.c:1244
do_syscall_64+0x31/0x40 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f3a30a7dec9
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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffeef521268 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f3a30cd4fa0 RCX: 00007f3a30a7dec9
RDX: 0000000000000000 RSI: 0000200000000100 RDI: ffffffffffffff9c
RBP: 00007f3a30b00f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f3a30cd4fa0 R14: 00007f3a30cd4fa0 R15: 0000000000000004
Modules linked in:
---[ end trace df04da23139645c1 ]---
RIP: 0010:ext4_es_end fs/ext4/extents_status.c:205 [inline]
RIP: 0010:__es_tree_search fs/ext4/extents_status.c:223 [inline]
RIP: 0010:ext4_es_cache_extent+0x4d6/0x5d0 fs/ext4/extents_status.c:972
Code: d2 ff e9 15 ff ff ff 44 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 8f fe ff ff 4c 89 f7 e8 84 ed d2 ff e9 82 fe ff ff e8 da fd 98 ff <0f> 0b 49 89 de 65 8b 05 7e 69 37 7e 89 c3 c1 e8 06 48 8d 3c c5 68
RSP: 0018:ffffc90000ec74c0 EFLAGS: 00010293
RAX: ffffffff81caa7c6 RBX: 0000000000000000 RCX: ffff88810f95e2c0
RDX: 0000000000000000 RSI: 000000000f95eb42 RDI: 0000000000000000
RBP: ffffc90000ec75e0 R08: 0000000000000004 R09: 0000000000000003
R10: fffff520001d8e88 R11: 1ffff920001d8e88 R12: 000000000f95eb42
R13: 1ffff11024b82a11 R14: ffff888125c1508c R15: dffffc0000000000
FS: 000055556be89500(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32a63fff CR3: 000000010f597000 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