====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 Not tainted ------------------------------------------------------ syz.5.270/8781 is trying to acquire lock: ffff88806b642270 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff88807a45a668 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->file.run_lock#2){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1119 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x232b/0x37c0 fs/ntfs3/inode.c:540 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl_raw+0x115/0x280 fs/namei.c:1689 lookup_one_qstr_excl fs/namei.c:1711 [inline] do_renameat2+0x401/0xc50 fs/namei.c:5222 __do_sys_rename fs/namei.c:5317 [inline] __se_sys_rename fs/namei.c:5315 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5315 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&wnd->rw_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1693 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x51f/0x3340 fs/ntfs3/inode.c:1268 ntfs_create+0x3d/0x50 fs/ntfs3/namei.c:110 lookup_open fs/namei.c:3701 [inline] open_last_lookups fs/namei.c:3800 [inline] path_openat+0x14f1/0x3830 fs/namei.c:4036 do_filp_open+0x1fa/0x410 fs/namei.c:4066 do_sys_openat2+0x121/0x1c0 fs/open.c:1429 do_sys_open fs/open.c:1444 [inline] __do_sys_openat fs/open.c:1460 [inline] __se_sys_openat fs/open.c:1455 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1455 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); *** DEADLOCK *** 5 locks held by syz.5.270/8781: #0: ffff88806b644420 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556 #1: ffff88805baba0f8 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #1: ffff88805baba0f8 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: open_last_lookups fs/namei.c:3797 [inline] #1: ffff88805baba0f8 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: path_openat+0x8da/0x3830 fs/namei.c:4036 #2: ffff88805bab9e60 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1110 [inline] #2: ffff88805bab9e60 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_create_inode+0x166/0x3340 fs/ntfs3/inode.c:1182 #3: ffff88806b642128 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x163/0xd50 fs/ntfs3/fsntfs.c:571 #4: ffff88807a45a668 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511 stack backtrace: CPU: 0 UID: 0 PID: 8781 Comm: syz.5.270 Not tainted 6.15.0-rc5-syzkaller-00043-gd76bb1ebb558 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/29/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2079 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3909 __lock_acquire+0xaac/0xd20 kernel/locking/lockdep.c:5235 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5866 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1693 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x51f/0x3340 fs/ntfs3/inode.c:1268 ntfs_create+0x3d/0x50 fs/ntfs3/namei.c:110 lookup_open fs/namei.c:3701 [inline] open_last_lookups fs/namei.c:3800 [inline] path_openat+0x14f1/0x3830 fs/namei.c:4036 do_filp_open+0x1fa/0x410 fs/namei.c:4066 do_sys_openat2+0x121/0x1c0 fs/open.c:1429 do_sys_open fs/open.c:1444 [inline] __do_sys_openat fs/open.c:1460 [inline] __se_sys_openat fs/open.c:1455 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1455 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f532cf8e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f532dd21038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f532d1b6080 RCX: 00007f532cf8e969 RDX: 000000000000275a RSI: 00002000000003c0 RDI: ffffffffffffff9c RBP: 00007f532d010ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000001 R14: 00007f532d1b6080 R15: 00007ffe93c5f018