option from the mount to silence this warning. ======================================================= JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.17/4420 is trying to acquire lock: ffff88803036d488 (&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: ffff8880693e0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] ffff8880693e0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x6c0/0x4ac0 fs/ocfs2/dir.c:3200 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_suballoc_bits+0x12e/0x4810 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x412/0x9a0 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0xcf8/0x4ac0 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x323a/0x5660 fs/ocfs2/dir.c:4321 ocfs2_rename+0x1938/0x3950 fs/ocfs2/namei.c:1478 vfs_rename+0xbe1/0x1100 fs/namei.c:4882 do_renameat2+0x8e5/0xce0 fs/namei.c:5035 __do_sys_rename fs/namei.c:5081 [inline] __se_sys_rename fs/namei.c:5079 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5079 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 *** 3 locks held by syz.0.17/4420: #0: ffff88801fe66460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff8880693e09c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #1: ffff8880693e09c8 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x435/0xce0 fs/namei.c:4974 #2: ffff8880693e0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] #2: ffff8880693e0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x6c0/0x4ac0 fs/ocfs2/dir.c:3200 stack backtrace: CPU: 0 PID: 4420 Comm: syz.0.17 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026 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_suballoc_bits+0x12e/0x4810 fs/ocfs2/suballoc.c:776 ocfs2_reserve_new_metadata_blocks+0x412/0x9a0 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2838 [inline] ocfs2_extend_dir+0xcf8/0x4ac0 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x323a/0x5660 fs/ocfs2/dir.c:4321 ocfs2_rename+0x1938/0x3950 fs/ocfs2/namei.c:1478 vfs_rename+0xbe1/0x1100 fs/namei.c:4882 do_renameat2+0x8e5/0xce0 fs/namei.c:5035 __do_sys_rename fs/namei.c:5081 [inline] __se_sys_rename fs/namei.c:5079 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5079 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:0x7f237e79c819 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:00007ffe8aeefd48 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007f237ea15fa0 RCX: 00007f237e79c819 RDX: 0000000000000000 RSI: 0000200000000f40 RDI: 00002000000003c0 RBP: 00007f237e832c91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f237ea15fac R14: 00007f237ea15fa0 R15: 00007f237ea15fa0 syz.0.17 (4420) used greatest stack depth: 18480 bytes left