JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode.
==================================================================
BUG: KASAN: use-after-free in ocfs2_find_victim_chain fs/ocfs2/suballoc.c:1391 [inline]
BUG: KASAN: use-after-free in ocfs2_claim_suballoc_bits+0x88c/0x1b74 fs/ocfs2/suballoc.c:1927
Read of size 4 at addr ffff0000de6f9000 by task syz.3.82/4489

CPU: 0 PID: 4489 Comm: syz.3.82 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call trace:
 dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack+0x30/0x40 lib/dump_stack.c:88
 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106
 print_address_description+0x78/0x30c mm/kasan/report.c:248
 __kasan_report mm/kasan/report.c:434 [inline]
 kasan_report+0xec/0x15c mm/kasan/report.c:451
 __asan_report_load4_noabort+0x44/0x50 mm/kasan/report_generic.c:308
 ocfs2_find_victim_chain fs/ocfs2/suballoc.c:1391 [inline]
 ocfs2_claim_suballoc_bits+0x88c/0x1b74 fs/ocfs2/suballoc.c:1927
 __ocfs2_claim_clusters+0x26c/0x7e0 fs/ocfs2/suballoc.c:2338
 ocfs2_claim_clusters+0x8c/0xd4 fs/ocfs2/suballoc.c:2375
 ocfs2_local_alloc_new_window fs/ocfs2/localalloc.c:1170 [inline]
 ocfs2_local_alloc_slide_window fs/ocfs2/localalloc.c:1299 [inline]
 ocfs2_reserve_local_alloc_bits+0x1188/0x260c fs/ocfs2/localalloc.c:668
 ocfs2_reserve_clusters_with_limit+0x198/0x9e0 fs/ocfs2/suballoc.c:1162
 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline]
 ocfs2_lock_allocators+0x27c/0x518 fs/ocfs2/suballoc.c:2669
 ocfs2_write_begin_nolock+0x1e88/0x3764 fs/ocfs2/aops.c:1741
 ocfs2_write_begin+0x1b4/0x30c fs/ocfs2/aops.c:1905
 generic_perform_write+0x204/0x480 mm/filemap.c:3785
 __generic_file_write_iter+0x23c/0x454 mm/filemap.c:3912
 ocfs2_file_write_iter+0x12e0/0x1b84 fs/ocfs2/file.c:2472
 call_write_iter include/linux/fs.h:2172 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x7c8/0xa2c fs/read_write.c:594
 ksys_pwrite64 fs/read_write.c:701 [inline]
 __do_sys_pwrite64 fs/read_write.c:711 [inline]
 __se_sys_pwrite64 fs/read_write.c:708 [inline]
 __arm64_sys_pwrite64+0x170/0x200 fs/read_write.c:708
 __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+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the page:
page:00000000ec039c28 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x11e6f9
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc000379be88 fffffc0003b9ab88 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000de6f8f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000de6f8f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000de6f9000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff0000de6f9080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff0000de6f9100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================