======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.6.1205/28824 is trying to acquire lock:
ffff88802ba40858 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7c4/0x10b0

but task is already holding lock:
ffff88802ba40c90 (mapping.invalidate_lock#14){++++}-{4:4}, at: ntfs_fallocate+0x3b8/0x10b0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (mapping.invalidate_lock#14){++++}-{4:4}:
       lock_acquire+0x120/0x360
       down_read+0x46/0x2e0
       filemap_fault+0x548/0x1200
       __do_fault+0x138/0x390
       __handle_mm_fault+0x3611/0x5440
       handle_mm_fault+0x40a/0x8e0
       do_user_addr_fault+0xa81/0x1390
       exc_page_fault+0x76/0xf0
       asm_exc_page_fault+0x26/0x30

-> #2 (vm_lock){++++}-{0:0}:
       lock_acquire+0x120/0x360
       __vma_enter_locked+0x182/0x380
       __vma_start_write+0x1e/0x120
       mprotect_fixup+0x578/0x9c0
       setup_arg_pages+0x53a/0xaa0
       load_elf_binary+0xba4/0x2740
       bprm_execve+0x99c/0x1450
       kernel_execve+0x8f0/0x9f0
       try_to_run_init_process+0x13/0x60
       kernel_init+0xad/0x1d0
       ret_from_fork+0x3fc/0x770
       ret_from_fork_asm+0x1a/0x30

-> #1 (&mm->mmap_lock){++++}-{4:4}:
       lock_acquire+0x120/0x360
       __might_fault+0xcc/0x130
       _copy_to_user+0x2c/0xb0
       fiemap_fill_next_extent+0x1c0/0x390
       ni_fiemap+0x89c/0xbf0
       ntfs_fiemap+0x11d/0x1a0
       do_vfs_ioctl+0x1173/0x1430
       __se_sys_ioctl+0x82/0x170
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&ni->ni_lock/5){+.+.}-{4:4}:
       validate_chain+0xb9b/0x2140
       __lock_acquire+0xab9/0xd20
       lock_acquire+0x120/0x360
       __mutex_lock+0x187/0x1350
       ntfs_fallocate+0x7c4/0x10b0
       vfs_fallocate+0x669/0x7e0
       __x64_sys_fallocate+0xc0/0x110
       do_syscall_64+0xfa/0x3b0
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

Chain exists of:
  &ni->ni_lock/5 --> vm_lock --> mapping.invalidate_lock#14

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(mapping.invalidate_lock#14);
                               lock(vm_lock);
                               lock(mapping.invalidate_lock#14);
  lock(&ni->ni_lock/5);

 *** DEADLOCK ***

3 locks held by syz.6.1205/28824:
 #0: ffff888029d5a428 (sb_writers#36){.+.+}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0
 #1: ffff88802ba40af0 (&sb->s_type->i_mutex_key#49){+.+.}-{4:4}, at: ntfs_fallocate+0x2ee/0x10b0
 #2: ffff88802ba40c90 (mapping.invalidate_lock#14){++++}-{4:4}, at: ntfs_fallocate+0x3b8/0x10b0

stack backtrace:
CPU: 1 UID: 0 PID: 28824 Comm: syz.6.1205 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
 __mutex_lock+0x187/0x1350
 ntfs_fallocate+0x7c4/0x10b0
 vfs_fallocate+0x669/0x7e0
 __x64_sys_fallocate+0xc0/0x110
 do_syscall_64+0xfa/0x3b0
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb63d18ebe9
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:00007fb63df7d038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fb63d3c6090 RCX: 00007fb63d18ebe9
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000006
RBP: 00007fb63d211e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb63d3c6128 R14: 00007fb63d3c6090 R15: 00007ffd61039b48
 </TASK>
