[v5.15] kernel panic: EXT4-fs (device loop0): panic forced after error

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 80efc6265290 Linux 5.15.150
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12816a2e180000
kernel config: https://syzkaller.appspot.com/x/.config?x=ca39ec49d1cf2068
dashboard link: https://syzkaller.appspot.com/bug?extid=9a5d91066721eed10205
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11df6f6a180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1221edf2180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/47cbb3459f23/disk-80efc626.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/40559d394d5f/vmlinux-80efc626.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b59e1390e778/Image-80efc626.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/460478534ecf/mount_0.gz

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

EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1053: 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-executor631: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 1 PID: 3960 Comm: syz-executor631 Not tainted 5.15.150-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
dump_stack+0x1c/0x58 lib/dump_stack.c:113
panic+0x304/0x8b4 kernel/panic.c:309
__ext4_error_inode+0x0/0x338 fs/ext4/super.c:667
__ext4_error+0x178/0x248 fs/ext4/super.c:756
ext4_validate_block_bitmap+0xd98/0x1114
ext4_wait_block_bitmap+0x194/0x1e0 fs/ext4/balloc.c:579
ext4_read_block_bitmap+0x54/0xe8 fs/ext4/balloc.c:591
ext4_mb_clear_bb fs/ext4/mballoc.c:6034 [inline]
ext4_free_blocks+0xd48/0x2bf0 fs/ext4/mballoc.c:6279
ext4_remove_blocks fs/ext4/extents.c:2519 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2685 [inline]
ext4_ext_remove_space+0x1c48/0x4254 fs/ext4/extents.c:2933
ext4_ext_truncate+0x188/0x250 fs/ext4/extents.c:4448
ext4_truncate+0x9c4/0x1058 fs/ext4/inode.c:4238
ext4_process_orphan+0x180/0x2b8 fs/ext4/orphan.c:339
ext4_orphan_cleanup+0x8bc/0x1048 fs/ext4/orphan.c:474
ext4_fill_super+0x8044/0x8768 fs/ext4/super.c:4966
mount_bdev+0x274/0x370 fs/super.c:1387
ext4_mount+0x44/0x58 fs/ext4/super.c:6582
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1517
do_new_mount+0x278/0x8fc fs/namespace.c:3005
path_mount+0x594/0x101c fs/namespace.c:3335
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount fs/namespace.c:3533 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3533
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0,000081c1,21302e40
Memory Limit: none
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 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