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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 69e434a1cb21 Linux 6.1.63
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17a87967680000
kernel config: https://syzkaller.appspot.com/x/.config?x=8936a912d77a129d
dashboard link: https://syzkaller.appspot.com/bug?extid=d940ca48e153ad86cb0f
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=16893458e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12d4318f680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8f4c34d49102/disk-69e434a1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/415c50ae270f/vmlinux-69e434a1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/71f602f135dc/Image-69e434a1.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fba3c9522c67/mount_0.gz

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

EXT4-fs warning (device loop0): ext4_update_dynamic_rev:1085: 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-executor238: bg 0: block 46: invalid block bitmap
Kernel panic - not syncing: EXT4-fs (device loop0): panic forced after error
CPU: 1 PID: 4221 Comm: syz-executor238 Not tainted 6.1.63-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__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+0x300/0x7fc kernel/panic.c:339
ext4_handle_error+0x750/0x798 fs/ext4/super.c:686
__ext4_error+0x20c/0x2dc fs/ext4/super.c:777
ext4_validate_block_bitmap+0xc6c/0xfd0
ext4_wait_block_bitmap+0x18c/0x1cc fs/ext4/balloc.c:580
ext4_read_block_bitmap+0x54/0xd4 fs/ext4/balloc.c:592
ext4_mb_clear_bb fs/ext4/mballoc.c:5991 [inline]
ext4_free_blocks+0xd3c/0x2b68 fs/ext4/mballoc.c:6236
ext4_remove_blocks fs/ext4/extents.c:2545 [inline]
ext4_ext_rm_leaf fs/ext4/extents.c:2711 [inline]
ext4_ext_remove_space+0x1bd0/0x4544 fs/ext4/extents.c:2959
ext4_ext_truncate+0x168/0x210 fs/ext4/extents.c:4417
ext4_truncate+0xa08/0x1178 fs/ext4/inode.c:4265
ext4_process_orphan+0x180/0x2b8 fs/ext4/orphan.c:339
ext4_orphan_cleanup+0x974/0x1134 fs/ext4/orphan.c:474
__ext4_fill_super fs/ext4/super.c:5533 [inline]
ext4_fill_super+0x6f04/0x7570 fs/ext4/super.c:5664
get_tree_bdev+0x360/0x54c fs/super.c:1355
ext4_get_tree+0x28/0x38 fs/ext4/super.c:5694
vfs_get_tree+0x90/0x274 fs/super.c:1562
do_new_mount+0x25c/0x8c4 fs/namespace.c:3040
path_mount+0x590/0xe5c fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x00000,02070084,26017203
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