[Android 5.15] kernel panic: EXT4-fs (device loop5): panic forced after error

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ea586874d2f9 Merge 5.15.131 into android13-5.15-lts
git tree: android13-5.15-lts
console output: https://syzkaller.appspot.com/x/log.txt?x=1739b230680000
kernel config: https://syzkaller.appspot.com/x/.config?x=8c01766ad16ac177
dashboard link: https://syzkaller.appspot.com/bug?extid=e35b543958ad678cd305
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=141b9402680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162a1fc8680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e84dfa4dc7ef/disk-ea586874.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b16cac25a266/vmlinux-ea586874.xz
kernel image: https://storage.googleapis.com/syzbot-assets/8aee32c39a67/bzImage-ea586874.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/dfbd26021969/mount_0.gz

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

Kernel panic - not syncing: EXT4-fs (device loop5): panic forced after error
CPU: 0 PID: 295 Comm: syz-executor129 Not tainted 5.15.131-syzkaller-00653-gea586874d2f9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x17 lib/dump_stack.c:113
panic+0x287/0x751 kernel/panic.c:309
ext4_handle_error+0x779/0x780 fs/ext4/super.c:667
__ext4_error+0x1ae/0x3d0 fs/ext4/super.c:756
ext4_validate_block_bitmap+0x1075/0x1410
ext4_wait_block_bitmap+0x1b2/0x1d0 fs/ext4/balloc.c:579
ext4_read_block_bitmap+0x41/0x80 fs/ext4/balloc.c:591
ext4_mb_clear_bb fs/ext4/mballoc.c:6009 [inline]
ext4_free_blocks+0xf32/0x2ab0 fs/ext4/mballoc.c:6254
ext4_remove_blocks fs/ext4/extents.c:2543 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2709 [inline]
ext4_ext_remove_space+0x267c/0x4a60 fs/ext4/extents.c:2957
ext4_ext_truncate+0x19a/0x240 fs/ext4/extents.c:4419
ext4_truncate+0x96c/0xfa0 fs/ext4/inode.c:4269
ext4_process_orphan+0x1d3/0x2f0 fs/ext4/orphan.c:339
ext4_orphan_cleanup+0x909/0x1060 fs/ext4/orphan.c:474
ext4_fill_super+0x8dc8/0x96e0 fs/ext4/super.c:4965
mount_bdev+0x282/0x3b0 fs/super.c:1387
ext4_mount+0x34/0x40 fs/ext4/super.c:6581
legacy_get_tree+0xf1/0x190 fs/fs_context.c:611
vfs_get_tree+0x88/0x290 fs/super.c:1517
do_new_mount+0x28b/0xad0 fs/namespace.c:2994
path_mount+0x671/0x1070 fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3522
__x64_sys_mount+0xbf/0xd0 fs/namespace.c:3522
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f951a509bc9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 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:00007ffe11fbbeb8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007f951a509bc9
RDX: 00000000200001c0 RSI: 00000000200006c0 RDI: 0000000020000640
RBP: 00000000000f4240 R08: 0000000000000000 R09: 00005555565d8378
R10: 000000003f000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe11fbbef0 R14: 00007ffe11fbbedc R15: 00007f951a55203b
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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 bug is already fixed, 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 bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup