======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.2.398/10385 is trying to acquire lock:
ffff888112fc0278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x638/0xb90

but task is already holding lock:
ffff8880211e4338 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x38e/0x1660

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->file.run_lock#2){++++}-{4:4}:
       down_read+0x47/0x2e0
       run_unpack_ex+0x7fa/0xb90
       ntfs_iget5+0x2416/0x38f0
       dir_search_u+0x1fd/0x2e0
       ntfs_lookup+0xfb/0x1f0
       __lookup_slow+0x2b7/0x410
       lookup_slow+0x53/0x70
       path_lookupat+0x3f5/0x8c0
       filename_lookup+0x256/0x5d0
       user_path_at+0x3a/0x60
       __se_sys_mount+0x2dc/0x420
       do_syscall_64+0xe2/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&wnd->rw_lock){++++}-{4:4}:
       __lock_acquire+0x15a5/0x2cf0
       lock_acquire+0x106/0x330
       down_read_nested+0x49/0x2e0
       run_unpack_ex+0x638/0xb90
       attr_collapse_range+0xb9a/0x1660
       ntfs_fallocate+0x801/0x1130
       vfs_fallocate+0x669/0x7e0
       __x64_sys_fallocate+0xc0/0x110
       do_syscall_64+0xe2/0xf80
       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);
  rlock(&wnd->rw_lock);

 *** DEADLOCK ***

5 locks held by syz.2.398/10385:
 #0: ffff888112fc2420 (sb_writers#14){++++}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0
 #1: ffff8880211e4520 (&sb->s_type->i_mutex_key#27){+.+.}-{4:4}, at: ntfs_fallocate+0x2ee/0x1130
 #2: ffff8880211e46c0 (mapping.invalidate_lock#5){++++}-{4:4}, at: ntfs_fallocate+0x3bd/0x1130
 #3: ffff8880211e4288 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7ed/0x1130
 #4: ffff8880211e4338 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x38e/0x1660

stack backtrace:
CPU: 0 UID: 0 PID: 10385 Comm: syz.2.398 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+0xe8/0x150
 print_circular_bug+0x2e1/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a5/0x2cf0
 lock_acquire+0x106/0x330
 down_read_nested+0x49/0x2e0
 run_unpack_ex+0x638/0xb90
 attr_collapse_range+0xb9a/0x1660
 ntfs_fallocate+0x801/0x1130
 vfs_fallocate+0x669/0x7e0
 __x64_sys_fallocate+0xc0/0x110
 do_syscall_64+0xe2/0xf80
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1d74f9acb9
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:00007f1d75da5028 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f1d75215fa0 RCX: 00007f1d74f9acb9
RDX: 0000000000002000 RSI: 0000000000000008 RDI: 0000000000000006
RBP: 00007f1d75008bf7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000010000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f1d75216038 R14: 00007f1d75215fa0 R15: 00007ffcd6efee38
 </TASK>
