JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,5) on (node local, slot 0) with ordered data mode. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.482/5909 is trying to acquire lock: ffff88805fe25108 (&sb->s_type->i_mutex_key#24/2){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline] ffff88805fe25108 (&sb->s_type->i_mutex_key#24/2){+.+.}-{3:3}, at: __ocfs2_reflink+0xca4/0x16d0 fs/ocfs2/refcounttree.c:4230 but task is already holding lock: ffff88805ff93f60 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_reflink+0x4cb/0x920 fs/ocfs2/refcounttree.c:4328 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&oi->ip_alloc_sem){++++}-{3:3}: down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ocfs2_inode_lock_for_extent_tree+0xd6/0x190 fs/ocfs2/file.c:2213 ocfs2_prepare_inode_for_write fs/ocfs2/file.c:2269 [inline] ocfs2_file_write_iter+0x6c6/0x1ee0 fs/ocfs2/file.c:2454 call_write_iter include/linux/fs.h:2179 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x748/0xd70 fs/read_write.c:594 ksys_write+0x153/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 -> #1 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}: down_write+0x38/0x60 kernel/locking/rwsem.c:1551 inode_lock include/linux/fs.h:793 [inline] vfs_rename+0x865/0x10f0 fs/namei.c:-1 do_renameat2+0x9e9/0xf70 fs/namei.c:5036 __do_sys_rename fs/namei.c:5082 [inline] __se_sys_rename fs/namei.c:5080 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5080 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 (&sb->s_type->i_mutex_key#24 /2){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3120 [inline] check_prevs_add kernel/locking/lockdep.c:3239 [inline] validate_chain kernel/locking/lockdep.c:3855 [inline] __lock_acquire+0x38f7/0x7d40 kernel/locking/lockdep.c:5120 lock_acquire+0x19f/0x400 kernel/locking/lockdep.c:5737 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:828 [inline] __ocfs2_reflink+0xca4/0x16d0 fs/ocfs2/refcounttree.c:4230 ocfs2_reflink+0x4e4/0x920 fs/ocfs2/refcounttree.c:4329 ocfs2_vfs_reflink+0x333/0x450 fs/ocfs2/refcounttree.c:4455 ocfs2_reflink_ioctl+0x39c/0x440 fs/ocfs2/refcounttree.c:4495 ocfs2_ioctl+0x586/0x7a0 fs/ocfs2/ioctl.c:913 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 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 other info that might help us debug this: Chain exists of: &sb->s_type->i_mutex_key#24/2 --> &sb->s_type->i_mutex_key#25 --> &oi->ip_alloc_sem Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&oi->ip_alloc_sem); lock(&sb->s_type->i_mutex_key#25); lock(&oi->ip_alloc_sem); lock(&sb->s_type->i_mutex_key#24/2); *** DEADLOCK *** 5 locks held by syz.5.482/5909: #0: ffff88807de4a460 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:386 #1: ffff88805fef2648 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:828 [inline] #1: ffff88805fef2648 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: filename_create+0x20b/0x450 fs/namei.c:3886 #2: ffff88805ff942c8 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3} , at: inode_lock include/linux/fs.h:793 [inline] , at: ocfs2_vfs_reflink+0x2f3/0x450 fs/ocfs2/refcounttree.c:4452 #3: ffff88805ff93ff8 (&oi->ip_xattr_sem){++++}-{3:3}, at: ocfs2_reflink+0x4bc/0x920 fs/ocfs2/refcounttree.c:4327 #4: ffff88805ff93f60 (&oi->ip_alloc_sem){++++}-{3:3}, at: ocfs2_reflink+0x4cb/0x920 fs/ocfs2/refcounttree.c:4328 stack backtrace: CPU: 1 PID: 5909 Comm: syz.5.482 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026 Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x2f8/0x400 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3120 [inline] check_prevs_add kernel/locking/lockdep.c:3239 [inline] validate_chain kernel/locking/lockdep.c:3855 [inline] __lock_acquire+0x38f7/0x7d40 kernel/locking/lockdep.c:5120 lock_acquire+0x19f/0x400 kernel/locking/lockdep.c:5737 down_write_nested+0x3b/0x60 kernel/locking/rwsem.c:1667 inode_lock_nested include/linux/fs.h:828 [inline] __ocfs2_reflink+0xca4/0x16d0 fs/ocfs2/refcounttree.c:4230 ocfs2_reflink+0x4e4/0x920 fs/ocfs2/refcounttree.c:4329 ocfs2_vfs_reflink+0x333/0x450 fs/ocfs2/refcounttree.c:4455 ocfs2_reflink_ioctl+0x39c/0x440 fs/ocfs2/refcounttree.c:4495 ocfs2_ioctl+0x586/0x7a0 fs/ocfs2/ioctl.c:913 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:874 [inline] __se_sys_ioctl+0xfa/0x170 fs/ioctl.c:860 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 RIP: 0033:0x7f2dbbccab19 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:00007f2db9f21028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f2dbbf50fa0 RCX: 00007f2dbbccab19 RDX: 0000200000009180 RSI: 0000000040186f04 RDI: 0000000000000004 RBP: 00007f2dbbd62b70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f2dbbf51038 R14: 00007f2dbbf50fa0 R15: 00007ffef6ac44d8 kcov: kcov_task_exit: t = ffff88807de6bb80, kcov->t = ffff88807de6bb80