======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.114/6658 is trying to acquire lock:
ffff88805d9e2800 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135

but task is already holding lock:
ffff888067280258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x732/0xb90 fs/ntfs3/run.c:1116

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&wnd->rw_lock){++++}-{4:4}:
       down_write_nested+0x3e/0x60 kernel/locking/rwsem.c:1706
       ntfs_look_for_free_space+0xd9/0x650 fs/ntfs3/fsntfs.c:362
       attr_allocate_clusters+0x1bd/0x6b0 fs/ntfs3/attrib.c:159
       attr_set_size+0x14cf/0x2cf0 fs/ntfs3/attrib.c:574
       ntfs_set_size+0x164/0x200 fs/ntfs3/inode.c:863
       ntfs_extend+0x1d9/0x9c0 fs/ntfs3/file.c:435
       ntfs_file_write_iter+0x424/0x870 fs/ntfs3/file.c:1314
       new_sync_write fs/read_write.c:595 [inline]
       vfs_write+0x629/0xba0 fs/read_write.c:688
       ksys_pwrite64 fs/read_write.c:795 [inline]
       __do_sys_pwrite64 fs/read_write.c:803 [inline]
       __se_sys_pwrite64 fs/read_write.c:800 [inline]
       __x64_sys_pwrite64+0x19c/0x230 fs/read_write.c:800
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->file.run_lock#2){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3165 [inline]
       check_prevs_add kernel/locking/lockdep.c:3284 [inline]
       validate_chain kernel/locking/lockdep.c:3908 [inline]
       __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
       down_read+0x97/0x200 kernel/locking/rwsem.c:1537
       run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x2416/0x38f0 fs/ntfs3/inode.c:542
       dir_search_u+0x1fd/0x2e0 fs/ntfs3/dir.c:265
       ntfs_lookup+0x100/0x1d0 fs/ntfs3/namei.c:85
       lookup_one_qstr_excl+0x131/0x360 fs/namei.c:1805
       __start_renaming+0x186/0x410 fs/namei.c:3856
       filename_renameat2+0x38c/0x9c0 fs/namei.c:6119
       __do_sys_rename fs/namei.c:6188 [inline]
       __se_sys_rename+0x55/0x2c0 fs/namei.c:6184
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x14d/0xf80 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(&wnd->rw_lock);
                               lock(&ni->file.run_lock#2);
                               lock(&wnd->rw_lock);
  rlock(&ni->file.run_lock#2);

 *** DEADLOCK ***

4 locks held by syz.2.114/6658:
 #0: ffff888066c8a480 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493
 #1: ffff88805f9f1308 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline]
 #1: ffff88805f9f1308 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3756 [inline]
 #1: ffff88805f9f1308 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: __start_renaming+0x148/0x410 fs/namei.c:3852
 #2: ffff88805f9f1050 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline]
 #2: ffff88805f9f1050 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_lookup+0xf3/0x1d0 fs/ntfs3/namei.c:84
 #3: ffff888067280258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x732/0xb90 fs/ntfs3/run.c:1116

stack backtrace:
CPU: 1 UID: 0 PID: 6658 Comm: syz.2.114 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043
 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175
 check_prev_add kernel/locking/lockdep.c:3165 [inline]
 check_prevs_add kernel/locking/lockdep.c:3284 [inline]
 validate_chain kernel/locking/lockdep.c:3908 [inline]
 __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868
 down_read+0x97/0x200 kernel/locking/rwsem.c:1537
 run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135
 ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
 ntfs_iget5+0x2416/0x38f0 fs/ntfs3/inode.c:542
 dir_search_u+0x1fd/0x2e0 fs/ntfs3/dir.c:265
 ntfs_lookup+0x100/0x1d0 fs/ntfs3/namei.c:85
 lookup_one_qstr_excl+0x131/0x360 fs/namei.c:1805
 __start_renaming+0x186/0x410 fs/namei.c:3856
 filename_renameat2+0x38c/0x9c0 fs/namei.c:6119
 __do_sys_rename fs/namei.c:6188 [inline]
 __se_sys_rename+0x55/0x2c0 fs/namei.c:6184
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9072afbf79
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:00007f9070d4e028 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f9072d75fa0 RCX: 00007f9072afbf79
RDX: 0000000000000000 RSI: 0000200000000100 RDI: 0000200000000000
RBP: 00007f9072b927e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f9072d76038 R14: 00007f9072d75fa0 R15: 00007fffc80e5a38
 </TASK>