====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.821/7148 is trying to acquire lock: ffff888051435f48 (&sb->s_type->i_mutex_key#27){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline] ffff888051435f48 (&sb->s_type->i_mutex_key#27){+.+.}-{3:3}, at: vfs_rename+0x865/0x10f0 fs/namei.c:-1 but task is already holding lock: ffff888051436d88 (&sb->s_type->i_mutex_key#27/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] ffff888051436d88 (&sb->s_type->i_mutex_key#27/2){+.+.}-{3:3}, at: vfs_rename+0x7b1/0x10f0 fs/namei.c:4888 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&sb->s_type->i_mutex_key#27/2){+.+.}-{3:3}: down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689 inode_lock_nested include/linux/fs.h:799 [inline] __ocfs2_reflink+0xca4/0x16d0 fs/ocfs2/refcounttree.c:4202 ocfs2_reflink+0x4e4/0x920 fs/ocfs2/refcounttree.c:4301 ocfs2_vfs_reflink+0x333/0x450 fs/ocfs2/refcounttree.c:4427 ocfs2_reflink_ioctl+0x39c/0x440 fs/ocfs2/refcounttree.c:4467 ocfs2_ioctl+0x584/0x7c0 fs/ocfs2/ioctl.c:913 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:870 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:856 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 -> #1 (&oi->ip_alloc_sem){++++}-{3:3}: down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520 ocfs2_inode_lock_for_extent_tree+0xd6/0x190 fs/ocfs2/file.c:2210 ocfs2_prepare_inode_for_write fs/ocfs2/file.c:2266 [inline] ocfs2_file_write_iter+0x6eb/0x1fc0 fs/ocfs2/file.c:2451 call_write_iter include/linux/fs.h:2271 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x482/0x9a0 fs/read_write.c:584 ksys_write+0x14d/0x260 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 -> #0 (&sb->s_type->i_mutex_key#27){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5678 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:764 [inline] vfs_rename+0x865/0x10f0 fs/namei.c:-1 do_renameat2+0x8ac/0xc80 fs/namei.c:5078 __do_sys_rename fs/namei.c:5124 [inline] __se_sys_rename fs/namei.c:5122 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5122 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: Chain exists of: &sb->s_type->i_mutex_key#27 --> &oi->ip_alloc_sem --> &sb->s_type->i_mutex_key#27/2 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#27/2); lock(&oi->ip_alloc_sem); lock(&sb->s_type->i_mutex_key#27/2); lock(&sb->s_type->i_mutex_key#27); *** DEADLOCK *** 5 locks held by syz.3.821/7148: #0: ffff888028096460 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402 #1: ffff888028096748 (&type->s_vfs_rename_key#5){+.+.}-{3:3}, at: lock_rename fs/namei.c:3089 [inline] #1: ffff888028096748 (&type->s_vfs_rename_key#5){+.+.}-{3:3}, at: do_renameat2+0x36a/0xc80 fs/namei.c:5017 #2: ffff8880514f89c8 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] #2: ffff8880514f89c8 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: lock_two_directories fs/namei.c:-1 [inline] #2: ffff8880514f89c8 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3090 [inline] #2: ffff8880514f89c8 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: do_renameat2+0x401/0xc80 fs/namei.c:5017 #3: ffff888051435108 (&sb->s_type->i_mutex_key#27/5){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline] #3: ffff888051435108 (&sb->s_type->i_mutex_key#27/5){+.+.}-{3:3}, at: do_renameat2+0x43c/0xc80 fs/namei.c:5017 #4: ffff888051436d88 (&sb->s_type->i_mutex_key#27/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:799 [inline] #4: ffff888051436d88 (&sb->s_type->i_mutex_key#27/2){+.+.}-{3:3}, at: vfs_rename+0x7b1/0x10f0 fs/namei.c:4888 stack backtrace: CPU: 1 PID: 7148 Comm: syz.3.821 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/16/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:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2d18/0x7c40 kernel/locking/lockdep.c:5063 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5678 down_write+0x36/0x60 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:764 [inline] vfs_rename+0x865/0x10f0 fs/namei.c:-1 do_renameat2+0x8ac/0xc80 fs/namei.c:5078 __do_sys_rename fs/namei.c:5124 [inline] __se_sys_rename fs/namei.c:5122 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5122 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:0x7f0c5259e159 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:00007f0c534a3028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052 RAX: ffffffffffffffda RBX: 00007f0c52825fa0 RCX: 00007f0c5259e159 RDX: 0000000000000000 RSI: 0000200000000340 RDI: 0000200000000580 RBP: 00007f0c5263506b R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f0c52826038 R14: 00007f0c52825fa0 R15: 00007ffd46323878 (syz.3.821,7148,0):ocfs2_double_lock:1195 ERROR: status = -2 (syz.3.821,7148,0):ocfs2_rename:1304 ERROR: status = -2 (syz.3.821,7148,0):ocfs2_rename:1694 ERROR: status = -2