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.127/4975 is trying to acquire lock: ffff888054f66a20 (&oi->ip_alloc_sem/1){+.+.}-{3:3}, at: ocfs2_remap_file_range+0x3f0/0x740 fs/ocfs2/file.c:2695 but task is already holding lock: ffff888054f63f60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_remap_file_range+0x3d4/0x740 fs/ocfs2/file.c:2693 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (&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 -> #1 (&osb->system_file_mutex){+.+.}-{3:3}: __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:798 ocfs2_reserve_new_metadata_blocks+0x412/0x9a0 fs/ocfs2/suballoc.c:1000 ocfs2_create_refcount_tree+0x299/0x1370 fs/ocfs2/refcounttree.c:571 ocfs2_reflink_remap_blocks+0x313/0x1aa0 fs/ocfs2/refcounttree.c:4655 ocfs2_remap_file_range+0x4a7/0x740 fs/ocfs2/file.c:2703 vfs_copy_file_range+0xd93/0x14f0 fs/read_write.c:1518 __do_sys_copy_file_range fs/read_write.c:1596 [inline] __se_sys_copy_file_range+0x320/0x470 fs/read_write.c:1559 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 (&oi->ip_alloc_sem/1){+.+.}-{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:5676 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689 ocfs2_remap_file_range+0x3f0/0x740 fs/ocfs2/file.c:2695 vfs_copy_file_range+0xd93/0x14f0 fs/read_write.c:1518 __do_sys_copy_file_range fs/read_write.c:1596 [inline] __se_sys_copy_file_range+0x320/0x470 fs/read_write.c:1559 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: &oi->ip_alloc_sem/1 --> &osb->system_file_mutex --> &ocfs2_file_ip_alloc_sem_key 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(&oi->ip_alloc_sem/1); *** DEADLOCK *** 4 locks held by syz.5.127/4975: #0: ffff88807d7d6460 (sb_writers#16){.+.+}-{0:0}, at: vfs_copy_file_range+0x8b7/0x14f0 fs/read_write.c:1502 #1: ffff888054f642c8 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff888054f642c8 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: lock_two_nondirectories+0xf7/0x150 fs/inode.c:1208 #2: ffff888054f66d88 (&sb->s_type->i_mutex_key#23/4){+.+.}-{3:3}, at: ocfs2_reflink_inodes_lock+0x129/0xcc0 fs/ocfs2/refcounttree.c:4723 #3: ffff888054f63f60 (&ocfs2_file_ip_alloc_sem_key){++++}-{3:3}, at: ocfs2_remap_file_range+0x3d4/0x740 fs/ocfs2/file.c:2693 stack backtrace: CPU: 1 PID: 4975 Comm: syz.5.127 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: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:5676 down_write_nested+0x39/0x60 kernel/locking/rwsem.c:1689 ocfs2_remap_file_range+0x3f0/0x740 fs/ocfs2/file.c:2695 vfs_copy_file_range+0xd93/0x14f0 fs/read_write.c:1518 __do_sys_copy_file_range fs/read_write.c:1596 [inline] __se_sys_copy_file_range+0x320/0x470 fs/read_write.c:1559 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:0x7ff8a9f9de99 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:00007ff8aadaf028 EFLAGS: 00000246 ORIG_RAX: 0000000000000146 RAX: ffffffffffffffda RBX: 00007ff8aa225fa0 RCX: 00007ff8a9f9de99 RDX: 0000000000000004 RSI: 0000000000000000 RDI: 0000000000000006 RBP: 00007ff8aa033eaf R08: 0000020000000008 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ff8aa226038 R14: 00007ff8aa225fa0 R15: 00007ffc0e7da378