ntfs3(loop1): ino=1b, mi_enum_attr
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.1.455/8206 is trying to acquire lock:
ffff8881224d59d0 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x7e5/0xba0

but task is already holding lock:
ffff888037d72270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&wnd->rw_lock){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_write_nested+0x9d/0x200
       ntfs_look_for_free_space+0xd3/0x600
       attr_allocate_clusters+0x1c1/0x6d0
       attr_set_size+0x14a4/0x2c70
       ntfs_extend_mft+0x162/0x450
       ntfs_look_free_mft+0x5f8/0xd50
       ni_create_attr_list+0x8ff/0x13d0
       ni_ins_attr_ext+0x43e/0xb50
       ni_add_name+0x6df/0xc90
       ni_rename+0x4a/0x100
       ntfs_rename+0x735/0xbf0
       vfs_rename+0xbda/0xf00
       do_renameat2+0x6ce/0xa80
       __x64_sys_rename+0x82/0x90
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->file.run_lock#2){++++}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       run_unpack_ex+0x7e5/0xba0
       ntfs_iget5+0x232b/0x37c0
       dir_search_u+0x1df/0x2c0
       ntfs_lookup+0xfb/0x1f0
       lookup_one_qstr_excl+0x131/0x360
       filename_create+0x224/0x3c0
       do_mkdirat+0xa0/0x590
       __x64_sys_mkdir+0x6c/0x80
       do_syscall_64+0xfa/0x3b0
       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.1.455/8206:
 #0: ffff88802375a428 (sb_writers#21){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90
 #1: ffff8881224d7918 (&type->i_mutex_dir_key#13/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0
 #2: ffff8881224d7680 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_lookup+0xee/0x1f0
 #3: ffff888037d72270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0

stack backtrace:
CPU: 1 UID: 0 PID: 8206 Comm: syz.1.455 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250
 print_circular_bug+0x2ee/0x310
 check_noncircular+0x134/0x160
 validate_chain+0xb9b/0x2140
 __lock_acquire+0xab9/0xd20
 lock_acquire+0x120/0x360
 down_read+0x46/0x2e0
 run_unpack_ex+0x7e5/0xba0
 ntfs_iget5+0x232b/0x37c0
 dir_search_u+0x1df/0x2c0
 ntfs_lookup+0xfb/0x1f0
 lookup_one_qstr_excl+0x131/0x360
 filename_create+0x224/0x3c0
 do_mkdirat+0xa0/0x590
 __x64_sys_mkdir+0x6c/0x80
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f926a78eba9
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:00007f926b596038 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 00007f926a9d5fa0 RCX: 00007f926a78eba9
RDX: 0000000000000000 RSI: 0000000000000021 RDI: 00002000000003c0
RBP: 00007f926a811e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f926a9d6038 R14: 00007f926a9d5fa0 R15: 00007ffce9910fc8
 </TASK>
