======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.445/7508 is trying to acquire lock:
ffff8881ba7a8270 (&wnd->rw_lock){++++}-{4:4}, at: mark_as_free_ex+0x3e/0x390

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

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+0x11f/0x350
       down_read+0x46/0x2e0
       run_unpack_ex+0x7fa/0xb90
       ntfs_iget5+0x23b6/0x3870
       ntfs_read_hdr+0x7cf/0xc30
       ntfs_readdir+0xa83/0xe20
       iterate_dir+0x399/0x570
       __se_sys_getdents64+0xf1/0x280
       do_syscall_64+0xf0/0xfa0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&wnd->rw_lock){++++}-{4:4}:
       validate_chain+0xb9a/0x2130
       __lock_acquire+0xab8/0xd20
       lock_acquire+0x11f/0x350
       down_write_nested+0x9d/0x210
       mark_as_free_ex+0x3e/0x390
       run_deallocate_ex+0x19a/0x310
       attr_collapse_range+0xcb4/0x1800
       ntfs_fallocate+0x801/0x1130
       vfs_fallocate+0x669/0x7e0
       __x64_sys_fallocate+0xc0/0x110
       do_syscall_64+0xf0/0xfa0
       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.445/7508:
 #0: ffff88816ffd8420 (sb_writers#22){.+.+}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0
 #1: ffff88811e019970 (&sb->s_type->i_mutex_key#31){+.+.}-{4:4}, at: ntfs_fallocate+0x2ee/0x1130
 #2: ffff88811e019b10 (mapping.invalidate_lock#9){++++}-{4:4}, at: ntfs_fallocate+0x3bd/0x1130
 #3: ffff88811e0196d8 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7ed/0x1130
 #4: ffff88811e019788 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x3b0/0x1800

stack backtrace:
CPU: 1 UID: 0 PID: 7508 Comm: syz.5.445 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+0x1a9/0x280
 print_circular_bug+0x2ed/0x300
 check_noncircular+0x134/0x160
 validate_chain+0xb9a/0x2130
 __lock_acquire+0xab8/0xd20
 lock_acquire+0x11f/0x350
 down_write_nested+0x9d/0x210
 mark_as_free_ex+0x3e/0x390
 run_deallocate_ex+0x19a/0x310
 attr_collapse_range+0xcb4/0x1800
 ntfs_fallocate+0x801/0x1130
 vfs_fallocate+0x669/0x7e0
 __x64_sys_fallocate+0xc0/0x110
 do_syscall_64+0xf0/0xfa0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f09e419acb9
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:00007f09e4fd8028 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f09e4415fa0 RCX: 00007f09e419acb9
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 00007f09e4208bf7 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f09e4416038 R14: 00007f09e4415fa0 R15: 00007ffc922ac138
 </TASK>
