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.732/7101 is trying to acquire lock: ffff888029235488 (&osb->system_file_mutex){+.+.}-{3:3}, at: ocfs2_get_system_file_inode+0x1a2/0x820 fs/ocfs2/sysfile.c:101 but task is already holding lock: ffff8880543b0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] ffff8880543b0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x6b7/0x4c40 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+0x266/0x980 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+0x3a8/0x2080 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+0x34d/0x820 fs/ocfs2/sysfile.c:112 ocfs2_init_global_system_inodes+0x315/0x6e0 fs/ocfs2/super.c:457 ocfs2_initialize_super fs/ocfs2/super.c:2253 [inline] ocfs2_fill_super+0x2b5a/0x5020 fs/ocfs2/super.c:994 mount_bdev+0x28a/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+0x247/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+0x2c92/0x7bd0 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/0xae0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1a2/0x820 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+0xd70/0x4c40 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x3217/0x5600 fs/ocfs2/dir.c:4321 ocfs2_mknod+0xb46/0x2580 fs/ocfs2/namei.c:294 ocfs2_mkdir+0x1b6/0x4b0 fs/ocfs2/namei.c:657 vfs_mkdir+0x386/0x570 fs/namei.c:4114 do_mkdirat+0x1d8/0x440 fs/namei.c:4139 __do_sys_mkdirat fs/namei.c:4154 [inline] __se_sys_mkdirat fs/namei.c:4152 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4152 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.732/7101: #0: ffff888076b66460 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff8880543b09c8 (&type->i_mutex_dir_key#25/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #1: ffff8880543b09c8 (&type->i_mutex_dir_key#25/1){+.+.}-{3:3}, at: filename_create+0x20b/0x450 fs/namei.c:3884 #2: ffff8880543b0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_expand_inline_dir fs/ocfs2/dir.c:2819 [inline] #2: ffff8880543b0660 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_extend_dir+0x6b7/0x4c40 fs/ocfs2/dir.c:3200 stack backtrace: CPU: 1 PID: 7101 Comm: syz.0.732 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/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+0x2c92/0x7bd0 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/0xae0 kernel/locking/mutex.c:747 ocfs2_get_system_file_inode+0x1a2/0x820 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+0xd70/0x4c40 fs/ocfs2/dir.c:3200 ocfs2_prepare_dir_for_insert+0x3217/0x5600 fs/ocfs2/dir.c:4321 ocfs2_mknod+0xb46/0x2580 fs/ocfs2/namei.c:294 ocfs2_mkdir+0x1b6/0x4b0 fs/ocfs2/namei.c:657 vfs_mkdir+0x386/0x570 fs/namei.c:4114 do_mkdirat+0x1d8/0x440 fs/namei.c:4139 __do_sys_mkdirat fs/namei.c:4154 [inline] __se_sys_mkdirat fs/namei.c:4152 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4152 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:0x7ff993b9ccc7 Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 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:00007ff994b0be58 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007ff994b0bee0 RCX: 00007ff993b9ccc7 RDX: 00000000000001ff RSI: 00002000000000c0 RDI: 00000000ffffff9c RBP: 0000200000000200 R08: 0000200000000000 R09: 0000000000000000 R10: 0000200000000200 R11: 0000000000000246 R12: 00002000000000c0 R13: 00007ff994b0bea0 R14: 0000000000000000 R15: 0000000000000000