[Android 5.10] kernel panic: EXT4-fs (device loop0): panic forced after error (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8a427269c016 Merge branch 'android13-5.10' into branch 'an..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1465293ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fefd86e1c1b1e951
dashboard link: https://syzkaller.appspot.com/bug?extid=e9caa43f4f89b426598a
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=162fae3da80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17536d3ba80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/42a188936754/disk-8a427269.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0d4218277015/vmlinux-8a427269.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a504bff7c461/bzImage-8a427269.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f58eba162415/mount_0.gz

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

EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1047: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs error (device loop0): ext4_validate_block_bitmap:429: comm syz-executor401: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 0 PID: 292 Comm: syz-executor401 Not tainted 5.10.187-syzkaller-00057-g8a427269c016 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack_lvl+0x1e2/0x24b lib/dump_stack.c:118
dump_stack+0x15/0x17 lib/dump_stack.c:135
panic+0x2cf/0x80b kernel/panic.c:308
ext4_handle_error+0x30e/0x310 fs/ext4/super.c:673
__ext4_error+0x203/0x420 fs/ext4/super.c:703
ext4_validate_block_bitmap+0xe5b/0x1010
ext4_wait_block_bitmap+0x1ac/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:5473 [inline]
ext4_free_blocks+0xdcb/0x27a0 fs/ext4/mballoc.c:5716
ext4_remove_blocks fs/ext4/extents.c:2538 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2704 [inline]
ext4_ext_remove_space+0x260f/0x4e10 fs/ext4/extents.c:2952
ext4_ext_truncate+0x17f/0x200 fs/ext4/extents.c:4413
ext4_truncate+0xb19/0x1220 fs/ext4/inode.c:4365
ext4_orphan_cleanup+0x8e4/0xd50 fs/ext4/super.c:3100
ext4_fill_super+0x89a5/0x9280 fs/ext4/super.c:5075
mount_bdev+0x262/0x370 fs/super.c:1420
ext4_mount+0x34/0x40 fs/ext4/super.c:6625
legacy_get_tree+0xf1/0x190 fs/fs_context.c:592
vfs_get_tree+0x88/0x290 fs/super.c:1550
do_new_mount+0x28b/0xad0 fs/namespace.c:2899
path_mount+0x56f/0xcb0 fs/namespace.c:3229
do_mount fs/namespace.c:3242 [inline]
__do_sys_mount fs/namespace.c:3450 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3427
__x64_sys_mount+0xbf/0xd0 fs/namespace.c:3427
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fe77597e1d9
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:00007ffcdc0092f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fe77597e1d9
RDX: 00000000200001c0 RSI: 00000000200006c0 RDI: 0000000020000640
RBP: 0000000000000000 R08: 0000000000000000 R09: 00007ffcdc009330
R10: 000000003f000000 R11: 0000000000000246 R12: 00007ffcdc009330
R13: 00007ffcdc0095b8 R14: 431bde82d7b634db R15: 00007fe7759c703b
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 change 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