JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,3) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.597/6421 is trying to acquire lock: ffff888079895488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x1b2/0x850 fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff88804ee46a20 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x19f/0x320 fs/ocfs2/aops.c:1902 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_read_virt_blocks+0x25d/0x970 fs/ocfs2/extent_map.c:984 ocfs2_read_dir_block fs/ocfs2/dir.c:508 [inline] ocfs2_find_entry_el fs/ocfs2/dir.c:715 [inline] ocfs2_find_entry+0x3c1/0x2180 fs/ocfs2/dir.c:1091 ocfs2_find_files_on_disk+0x102/0x390 fs/ocfs2/dir.c:1995 ocfs2_lookup_ino_from_name+0x4f/0xf0 fs/ocfs2/dir.c:2017 _ocfs2_get_system_file_inode fs/ocfs2/sysfile.c:136 [inline] ocfs2_get_system_file_inode+0x36a/0x850 fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x2f3/0x6d0 fs/ocfs2/super.c:457 ocfs2_initialize_super fs/ocfs2/super.c:2253 [inline] ocfs2_fill_super+0x2bc2/0x5090 fs/ocfs2/super.c:994 mount_bdev+0x287/0x3c0 fs/super.c:1443 legacy_get_tree+0xe6/0x180 fs/fs_context.c:632 vfs_get_tree+0x88/0x270 fs/super.c:1573 do_new_mount+0x24a/0xa40 fs/namespace.c:3078 do_mount fs/namespace.c:3421 [inline] __do_sys_mount fs/namespace.c:3629 [inline] __se_sys_mount+0x2e3/0x3d0 fs/namespace.c:3606 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&osb->system_file_mutex){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1b2/0x850 fs/ocfs2/sysfile.c:101 ocfs2_reserve_local_alloc_bits+0xfd/0x2700 fs/ocfs2/localalloc.c:626 ocfs2_reserve_clusters_with_limit+0x1b6/0xc10 fs/ocfs2/suballoc.c:1162 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline] ocfs2_lock_allocators+0x2d5/0x5f0 fs/ocfs2/suballoc.c:2679 ocfs2_write_begin_nolock+0x1b70/0x44f0 fs/ocfs2/aops.c:1740 ocfs2_write_begin+0x1c2/0x320 fs/ocfs2/aops.c:1904 generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862 __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960 ocfs2_file_write_iter+0x1660/0x1f00 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+0x4b1/0xa30 fs/read_write.c:584 ksys_write+0x14c/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); lock(&ocfs2_file_ip_alloc_sem_key); lock(&osb->system_file_mutex); *** DEADLOCK *** 4 locks held by syz.3.597/6421: #0: ffff88807c2a8ae8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038 #1: ffff888052a7e460 (sb_writers#16){.+.+}-{0:0}, at: vfs_write+0x26b/0xa30 fs/read_write.c:580 #2: ffff88804ee46d88 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff88804ee46d88 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: ocfs2_file_write_iter+0x448/0x1f00 fs/ocfs2/file.c:2399 #3: ffff88804ee46a20 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_write_begin+0x19f/0x320 fs/ocfs2/aops.c:1902 stack backtrace: CPU: 0 PID: 6421 Comm: syz.3.597 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x2d07/0x7d10 kernel/locking/lockdep.c:5049 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x12d/0xaf0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1b2/0x850 fs/ocfs2/sysfile.c:101 ocfs2_reserve_local_alloc_bits+0xfd/0x2700 fs/ocfs2/localalloc.c:626 ocfs2_reserve_clusters_with_limit+0x1b6/0xc10 fs/ocfs2/suballoc.c:1162 ocfs2_reserve_clusters fs/ocfs2/suballoc.c:1223 [inline] ocfs2_lock_allocators+0x2d5/0x5f0 fs/ocfs2/suballoc.c:2679 ocfs2_write_begin_nolock+0x1b70/0x44f0 fs/ocfs2/aops.c:1740 ocfs2_write_begin+0x1c2/0x320 fs/ocfs2/aops.c:1904 generic_perform_write+0x2fa/0x5c0 mm/filemap.c:3862 __generic_file_write_iter+0x148/0x2a0 mm/filemap.c:3960 ocfs2_file_write_iter+0x1660/0x1f00 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+0x4b1/0xa30 fs/read_write.c:584 ksys_write+0x14c/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7f021ed9acb9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f021fcc4028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00007f021f015fa0 RCX: 00007f021ed9acb9 RDX: 000000000000fdef RSI: 00002000000001c0 RDI: 0000000000000005 RBP: 00007f021ee08bf7 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f021f016038 R14: 00007f021f015fa0 R15: 00007fff2e3e8868 OCFS2: ERROR (device loop3): int ocfs2_validate_gd_parent(struct super_block *, struct ocfs2_dinode *, struct buffer_head *, int): Group descriptor #32 has bit count of 1024 On-disk corruption discovered. Please run fsck.ocfs2 once the filesystem is unmounted. OCFS2: File system is now read-only. (syz.3.597,6421,0):ocfs2_search_chain:1761 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_search_chain:1871 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_claim_suballoc_bits:1950 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_claim_suballoc_bits:1993 ERROR: status = -30 (syz.3.597,6421,0):__ocfs2_claim_clusters:2365 ERROR: status = -30 (syz.3.597,6421,0):__ocfs2_claim_clusters:2373 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_local_alloc_new_window:1203 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_local_alloc_new_window:1228 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_local_alloc_slide_window:1302 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_local_alloc_slide_window:1321 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_reserve_local_alloc_bits:671 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_reserve_local_alloc_bits:709 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_reserve_clusters_with_limit:1166 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_reserve_clusters_with_limit:1215 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_lock_allocators:2682 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_write_begin_nolock:1744 ERROR: status = -30 (syz.3.597,6421,0):ocfs2_write_begin:1907 ERROR: status = -30