====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.1743/10877 is trying to acquire lock: ffff8880590614a0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 but task is already holding lock: ffff888059061538 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa5/0x340 fs/ocfs2/refcounttree.c:931 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&oi->ip_xattr_sem){++++}-{3:3}: down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ocfs2_init_acl+0x30a/0x770 fs/ocfs2/acl.c:366 ocfs2_mknod+0x140f/0x2300 fs/ocfs2/namei.c:410 ocfs2_mkdir+0x196/0x430 fs/ocfs2/namei.c:657 vfs_mkdir+0x296/0x440 fs/namei.c:4121 do_mkdirat+0x1dc/0x450 fs/namei.c:4144 __do_sys_mkdirat fs/namei.c:4159 [inline] __se_sys_mkdirat fs/namei.c:4157 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4157 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #2 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ocfs2_start_trans+0x3a8/0x6f0 fs/ocfs2/journal.c:372 ocfs2_block_group_alloc fs/ocfs2/suballoc.c:681 [inline] ocfs2_reserve_suballoc_bits+0x7ad/0x44c0 fs/ocfs2/suballoc.c:828 ocfs2_reserve_new_metadata_blocks+0x416/0x9a0 fs/ocfs2/suballoc.c:978 ocfs2_expand_inline_dir fs/ocfs2/dir.c:2839 [inline] ocfs2_extend_dir+0xcca/0x48b0 fs/ocfs2/dir.c:3201 ocfs2_prepare_dir_for_insert+0x315b/0x56b0 fs/ocfs2/dir.c:4322 ocfs2_mknod+0x81b/0x2300 fs/ocfs2/namei.c:294 ocfs2_mkdir+0x196/0x430 fs/ocfs2/namei.c:657 vfs_mkdir+0x296/0x440 fs/namei.c:4121 do_mkdirat+0x1dc/0x450 fs/namei.c:4144 __do_sys_mkdirat fs/namei.c:4159 [inline] __se_sys_mkdirat fs/namei.c:4157 [inline] __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4157 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #1 (sb_internal#6){.+.+}-{0:0}: percpu_down_read include/linux/percpu-rwsem.h:51 [inline] __sb_start_write include/linux/fs.h:1633 [inline] sb_start_intwrite include/linux/fs.h:1755 [inline] ocfs2_start_trans+0x2a9/0x6f0 fs/ocfs2/journal.c:370 ocfs2_extend_dir+0x1113/0x48b0 fs/ocfs2/dir.c:3288 ocfs2_prepare_dx_dir_for_insert fs/ocfs2/dir.c:4236 [inline] ocfs2_prepare_dir_for_insert+0x3fdc/0x56b0 fs/ocfs2/dir.c:4298 ocfs2_mknod+0x81b/0x2300 fs/ocfs2/namei.c:294 ocfs2_create+0x196/0x430 fs/ocfs2/namei.c:674 vfs_create+0x1f4/0x360 fs/namei.c:3198 do_mknodat+0x3d0/0x500 fs/namei.c:4049 __do_sys_mknod fs/namei.c:4082 [inline] __se_sys_mknod fs/namei.c:4080 [inline] __x64_sys_mknod+0x8e/0xa0 fs/namei.c:4080 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xde5/0x1440 fs/ocfs2/file.c:521 ocfs2_setattr+0x158d/0x1bc0 fs/ocfs2/file.c:1211 notify_change+0xb0d/0xe10 fs/attr.c:499 do_truncate+0x1b0/0x240 fs/open.c:66 vfs_truncate+0x266/0x300 fs/open.c:112 do_sys_truncate+0xf6/0x1c0 fs/open.c:135 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 other info that might help us debug this: Chain exists of: &ocfs2_file_ip_alloc_sem_key --> &journal->j_trans_barrier --> &oi->ip_xattr_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_xattr_sem); lock(&journal->j_trans_barrier); lock(&oi->ip_xattr_sem); lock(&ocfs2_file_ip_alloc_sem_key); *** DEADLOCK *** 3 locks held by syz.2.1743/10877: #0: ffff8880597f2418 (sb_writers#31){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412 #1: ffff888059061818 (&sb->s_type->i_mutex_key#39){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #1: ffff888059061818 (&sb->s_type->i_mutex_key#39){+.+.}-{3:3}, at: do_truncate+0x19c/0x240 fs/open.c:64 #2: ffff888059061538 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa5/0x340 fs/ocfs2/refcounttree.c:931 stack backtrace: CPU: 0 PID: 10877 Comm: syz.2.1743 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026 Call Trace: dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106 check_noncircular+0x2fc/0x400 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2df1/0x7d40 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5754 down_write+0x97/0x200 kernel/locking/rwsem.c:1573 ocfs2_try_remove_refcount_tree+0xb7/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xde5/0x1440 fs/ocfs2/file.c:521 ocfs2_setattr+0x158d/0x1bc0 fs/ocfs2/file.c:1211 notify_change+0xb0d/0xe10 fs/attr.c:499 do_truncate+0x1b0/0x240 fs/open.c:66 vfs_truncate+0x266/0x300 fs/open.c:112 do_sys_truncate+0xf6/0x1c0 fs/open.c:135 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xa0 arch/x86/entry/common.c:76 entry_SYSCALL_64_after_hwframe+0x68/0xd2 RIP: 0033:0x7fbc30f9af79 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:00007fbc31da8028 EFLAGS: 00000246 ORIG_RAX: 000000000000004c RAX: ffffffffffffffda RBX: 00007fbc31215fa0 RCX: 00007fbc30f9af79 RDX: 0000000000000000 RSI: 0000000000008008 RDI: 00002000000000c0 RBP: 00007fbc310316e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fbc31216038 R14: 00007fbc31215fa0 R15: 00007ffdd7e059d8