====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:5/4275 is trying to acquire lock: ffff888071268660 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xb3/0x340 fs/ocfs2/refcounttree.c:932 but task is already holding lock: ffff8880712686f8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa1/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+0x44/0x2e0 kernel/locking/rwsem.c:1498 ocfs2_init_acl+0x307/0x770 fs/ocfs2/acl.c:365 ocfs2_mknod+0x15cb/0x2510 fs/ocfs2/namei.c:410 ocfs2_create+0x192/0x420 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3470 [inline] open_last_lookups fs/namei.c:3540 [inline] path_openat+0x11db/0x2fa0 fs/namei.c:3747 do_filp_open+0x1e2/0x410 fs/namei.c:3777 do_sys_openat2+0x150/0x4b0 fs/open.c:1255 do_sys_open fs/open.c:1271 [inline] __do_sys_openat fs/open.c:1287 [inline] __se_sys_openat fs/open.c:1282 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1282 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #2 (&journal->j_trans_barrier){.+.+}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ocfs2_start_trans+0x3a6/0x6f0 fs/ocfs2/journal.c:374 ocfs2_mknod+0xf5a/0x2510 fs/ocfs2/namei.c:361 ocfs2_create+0x192/0x420 fs/ocfs2/namei.c:674 lookup_open fs/namei.c:3470 [inline] open_last_lookups fs/namei.c:3540 [inline] path_openat+0x11db/0x2fa0 fs/namei.c:3747 do_filp_open+0x1e2/0x410 fs/namei.c:3777 do_sys_openat2+0x150/0x4b0 fs/open.c:1255 do_sys_open fs/open.c:1271 [inline] __do_sys_openat fs/open.c:1287 [inline] __se_sys_openat fs/open.c:1282 [inline] __x64_sys_openat+0x135/0x160 fs/open.c:1282 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #1 (sb_internal#3){.+.+}-{0:0}: __lock_release kernel/locking/lockdep.c:5339 [inline] lock_release+0x321/0x8a0 kernel/locking/lockdep.c:5643 up_write+0x29/0x420 kernel/locking/rwsem.c:1603 inode_unlock include/linux/fs.h:792 [inline] ocfs2_free_ac_resource fs/ocfs2/suballoc.c:126 [inline] ocfs2_free_alloc_context+0x93/0x1a0 fs/ocfs2/suballoc.c:140 ocfs2_write_begin_nolock+0x4382/0x4400 fs/ocfs2/aops.c:1826 ocfs2_write_begin+0x1b9/0x310 fs/ocfs2/aops.c:1905 generic_perform_write+0x2b6/0x550 mm/filemap.c:3785 __generic_file_write_iter+0x25f/0x4e0 mm/filemap.c:3912 ocfs2_file_write_iter+0x1670/0x1e70 fs/ocfs2/file.c:2472 call_write_iter include/linux/fs.h:2173 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x745/0xd60 fs/read_write.c:594 ksys_write+0x152/0x260 fs/read_write.c:647 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #0 (&oi->ip_alloc_sem){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ocfs2_try_remove_refcount_tree+0xb3/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xe03/0x1460 fs/ocfs2/file.c:517 ocfs2_recover_orphans fs/ocfs2/journal.c:2285 [inline] ocfs2_complete_recovery+0x128b/0x2120 fs/ocfs2/journal.c:1311 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 other info that might help us debug this: Chain exists of: &oi->ip_alloc_sem --> &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(&oi->ip_alloc_sem); *** DEADLOCK *** 4 locks held by kworker/u4:5/4275: #0: ffff88802424d938 ((wq_completion)ocfs2_wq){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1 #1: ffffc9000335fd00 ((work_completion)(&journal->j_recovery_work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285 #2: ffff8880712689c8 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline] #2: ffff8880712689c8 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: ocfs2_recover_orphans fs/ocfs2/journal.c:2266 [inline] #2: ffff8880712689c8 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: ocfs2_complete_recovery+0xff2/0x2120 fs/ocfs2/journal.c:1311 #3: ffff8880712686f8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_try_remove_refcount_tree+0xa1/0x340 fs/ocfs2/refcounttree.c:931 stack backtrace: CPU: 0 PID: 4275 Comm: kworker/u4:5 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: ocfs2_wq ocfs2_complete_recovery Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_write+0x38/0x60 kernel/locking/rwsem.c:1551 ocfs2_try_remove_refcount_tree+0xb3/0x340 fs/ocfs2/refcounttree.c:932 ocfs2_truncate_file+0xe03/0x1460 fs/ocfs2/file.c:517 ocfs2_recover_orphans fs/ocfs2/journal.c:2285 [inline] ocfs2_complete_recovery+0x128b/0x2120 fs/ocfs2/journal.c:1311 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287