[v6.1] kernel BUG in ocfs2_reserve_suballoc_bits

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 344a09659766 Linux 6.1.131
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=130d2474580000
kernel config: https://syzkaller.appspot.com/x/.config?x=14d5dbae75afa499
dashboard link: https://syzkaller.appspot.com/bug?extid=0bd0b59b490fa19f4998
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8c94453bbad3/disk-344a0965.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bf26518c790/vmlinux-344a0965.xz
kernel image: https://storage.googleapis.com/syzbot-assets/424da9a470eb/Image-344a0965.gz.xz

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

------------[ cut here ]------------
kernel BUG at fs/ocfs2/suballoc.c:800!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5784 Comm: syz.5.311 Not tainted 6.1.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_reserve_suballoc_bits+0x391c/0x4428 fs/ocfs2/suballoc.c:800
lr : ocfs2_reserve_suballoc_bits+0x391c/0x4428 fs/ocfs2/suballoc.c:800
sp : ffff800021956200
x29: ffff8000219566e0 x28: ffff0000f4fe4fb8 x27: ffff800021956620
x26: ffff0000fa3e1e00 x25: 0000000000000001 x24: 000000000000ffff
x23: dfff800000000000 x22: ffff70000432ac70 x21: 0000000000000000
x20: 00000000ffffffff x19: ffff800021956380 x18: ffff800021956360
x17: ffff800018c58000 x16: ffff8000122dd0e4 x15: 0000000000000002
x14: 1ffff00002b600b2 x13: dfff800000000000 x12: 0000000000080000
x11: 000000000007ffff x10: ffff80002650b000 x9 : ffff800009fea2c0
x8 : 0000000000080000 x7 : ffff800009f6f410 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000123fb894
x2 : 0000000000000000 x1 : 00000000ffffffff x0 : 0000000000000000
Call trace:
ocfs2_reserve_suballoc_bits+0x391c/0x4428 fs/ocfs2/suballoc.c:800
ocfs2_reserve_cluster_bitmap_bits+0xcc/0x1e0 fs/ocfs2/suballoc.c:1128
ocfs2_local_alloc_reserve_for_window fs/ocfs2/localalloc.c:1112 [inline]
ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1248 [inline]
ocfs2_reserve_local_alloc_bits+0x758/0x2610 fs/ocfs2/localalloc.c:668
ocfs2_reserve_clusters_with_limit+0x194/0xabc fs/ocfs2/suballoc.c:1162
ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline]
ocfs2_lock_allocators+0x294/0x584 fs/ocfs2/suballoc.c:2669
ocfs2_write_begin_nolock+0x22fc/0x3f6c fs/ocfs2/aops.c:1740
ocfs2_write_begin+0x1ac/0x38c fs/ocfs2/aops.c:1904
generic_perform_write+0x278/0x55c mm/filemap.c:3845
__generic_file_write_iter+0x168/0x388 mm/filemap.c:3973
ocfs2_file_write_iter+0x156c/0x1f48 fs/ocfs2/file.c:2469
call_write_iter include/linux/fs.h:2265 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x610/0x91c fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
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
Code: aa1803e0 97a6365b 17fff8c3 97942a50 (d4210000)
---[ end trace 0000000000000000 ]---


---
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 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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.