[Android 5.4] kernel BUG in __es_remove_extent (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1b3143b9b166 UPSTREAM: net: tls, update curr on splice as ..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13e856c2180000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2dd4b5d39d9fde5
dashboard link: https://syzkaller.appspot.com/bug?extid=2a58d88f0fb315c85363
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=157415fc180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1509c872180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/13b35a330e2d/disk-1b3143b9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/770086d9812a/vmlinux-1b3143b9.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2e40ab981be7/bzImage-1b3143b9.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/14ed18e0a2f7/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/extents_status.c:205!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 355 Comm: syz-executor343 Not tainted 5.4.265-syzkaller-00001-g1b3143b9b166 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:ext4_es_end fs/ext4/extents_status.c:205 [inline]
RIP: 0010:__es_remove_extent+0x1d98/0x1dd0 fs/ext4/extents_status.c:1437
Code: 07 80 c1 03 38 c1 0f 8c 57 f7 ff ff 48 8d bc 24 30 01 00 00 e8 e9 07 d1 ff e9 45 f7 ff ff e8 3f 35 a1 ff 0f 0b e8 38 35 a1 ff <0f> 0b e8 01 ee 77 ff e8 2c 35 a1 ff 0f 0b e8 25 35 a1 ff 0f 0b e8
RSP: 0018:ffff8881dbef6f00 EFLAGS: 00010293
RAX: ffffffff81c31188 RBX: 00000000ffffffff RCX: ffff8881dbf48fc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff8881dbef7110 R08: ffffffff81c2fe69 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff1103d1942dc
R13: 0000000000000001 R14: 0000000000000000 R15: dffffc0000000000
FS: 0000555556b17380(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556ffeb88da0 CR3: 00000001dbee8000 CR4: 00000000003406b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_es_insert_extent+0x465/0x2d70 fs/ext4/extents_status.c:892
ext4_map_blocks+0x641/0x1ba0 fs/ext4/inode.c:608
ext4_getblk+0x112/0x540 fs/ext4/inode.c:985
ext4_bread+0x89/0x390 fs/ext4/inode.c:1035
ext4_quota_read+0x180/0x280 fs/ext4/super.c:6187
v2_read_header fs/quota/quota_v2.c:64 [inline]
v2_check_quota_file+0xf7/0x490 fs/quota/quota_v2.c:83
dquot_load_quota_sb+0x6af/0xc00 fs/quota/dquot.c:2479
vfs_load_quota_inode+0x40b/0x6a0 fs/quota/dquot.c:2523
ext4_quota_enable fs/ext4/super.c:6066 [inline]
ext4_enable_quotas+0x5a8/0x940 fs/ext4/super.c:6092
ext4_fill_super+0x84f0/0x8d90 fs/ext4/super.c:4708
mount_bdev+0x267/0x370 fs/super.c:1426
legacy_get_tree+0xdf/0x170 fs/fs_context.c:648
vfs_get_tree+0x85/0x260 fs/super.c:1556
do_new_mount+0x292/0x570 fs/namespace.c:2843
do_mount+0x688/0xe10 fs/namespace.c:3163
ksys_mount+0xc2/0xf0 fs/namespace.c:3372
__do_sys_mount fs/namespace.c:3386 [inline]
__se_sys_mount fs/namespace.c:3383 [inline]
__x64_sys_mount+0xb1/0xc0 fs/namespace.c:3383
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace aee00b66e4148675 ]---
RIP: 0010:ext4_es_end fs/ext4/extents_status.c:205 [inline]
RIP: 0010:__es_remove_extent+0x1d98/0x1dd0 fs/ext4/extents_status.c:1437
Code: 07 80 c1 03 38 c1 0f 8c 57 f7 ff ff 48 8d bc 24 30 01 00 00 e8 e9 07 d1 ff e9 45 f7 ff ff e8 3f 35 a1 ff 0f 0b e8 38 35 a1 ff <0f> 0b e8 01 ee 77 ff e8 2c 35 a1 ff 0f 0b e8 25 35 a1 ff 0f 0b e8
RSP: 0018:ffff8881dbef6f00 EFLAGS: 00010293
RAX: ffffffff81c31188 RBX: 00000000ffffffff RCX: ffff8881dbf48fc0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffff8881dbef7110 R08: ffffffff81c2fe69 R09: 0000000000000003
R10: ffffffffffffffff R11: dffffc0000000001 R12: 1ffff1103d1942dc
R13: 0000000000000001 R14: 0000000000000000 R15: dffffc0000000000
FS: 0000555556b17380(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000556ffeb88da0 CR3: 00000001dbee8000 CR4: 00000000003406b0
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