======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.5.7032/24837 is trying to acquire lock:
ffff88801aec29a0 (mapping.invalidate_lock#9){++++}-{4:4}, at: filemap_fault+0x5c3/0x1290

but task is already holding lock:
ffff88816c192508 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1a7/0x4a0

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #3 (vm_lock){++++}-{0:0}:
       __vma_enter_locked+0x23a/0x730
       __vma_start_write+0x23/0x140
       mprotect_fixup+0x5af/0xa30
       setup_arg_pages+0x52a/0xa90
       load_elf_binary+0xba4/0x2740
       bprm_execve+0x92e/0x1400
       kernel_execve+0x8f0/0x9f0
       try_to_run_init_process+0x13/0x60
       kernel_init+0xad/0x1d0
       ret_from_fork+0x599/0xb30
       ret_from_fork_asm+0x1a/0x30

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

-> #1 (&ni->ni_lock#3/5){+.+.}-{4:4}:
       __mutex_lock+0x187/0x1350
       attr_data_get_block+0x2ec/0x1ec0
       ntfs_get_block_vbo+0x392/0xc30
       do_mpage_readpage+0x822/0x1990
       mpage_readahead+0x3b0/0x790
       read_pages+0x17a/0x580
       page_cache_ra_unbounded+0x630/0x990
       filemap_get_pages+0x468/0x1dc0
       filemap_splice_read+0x581/0xc60
       splice_direct_to_actor+0x4a9/0xcc0
       do_splice_direct+0x181/0x270
       vfs_copy_file_range+0xb03/0x1370
       __se_sys_copy_file_range+0x2fb/0x470
       do_syscall_64+0xfa/0xf80
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (mapping.invalidate_lock#9){++++}-{4:4}:
       __lock_acquire+0x15a6/0x2cf0
       lock_acquire+0x117/0x340
       down_read+0x47/0x2e0
       filemap_fault+0x5c3/0x1290
       __do_fault+0x138/0x390
       do_pte_missing+0x6aa/0x3330
       handle_mm_fault+0x1b26/0x32b0
       do_user_addr_fault+0xa7c/0x1380
       exc_page_fault+0x82/0x100
       asm_exc_page_fault+0x26/0x30

other info that might help us debug this:

Chain exists of:
  mapping.invalidate_lock#9 --> &mm->mmap_lock --> vm_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(vm_lock);
                               lock(&mm->mmap_lock);
                               lock(vm_lock);
  rlock(mapping.invalidate_lock#9);

 *** DEADLOCK ***

1 lock held by syz.5.7032/24837:
 #0: ffff88816c192508 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1a7/0x4a0

stack backtrace:
CPU: 1 UID: 0 PID: 24837 Comm: syz.5.7032 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
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+0x2e2/0x300
 check_noncircular+0x12e/0x150
 __lock_acquire+0x15a6/0x2cf0
 lock_acquire+0x117/0x340
 down_read+0x47/0x2e0
 filemap_fault+0x5c3/0x1290
 __do_fault+0x138/0x390
 do_pte_missing+0x6aa/0x3330
 handle_mm_fault+0x1b26/0x32b0
 do_user_addr_fault+0xa7c/0x1380
 exc_page_fault+0x82/0x100
 asm_exc_page_fault+0x26/0x30
RIP: 0033:0x7fbb470556b1
Code: 48 8b 54 24 08 48 85 d2 74 17 8b 44 24 18 0f c8 89 c0 48 89 44 24 18 48 83 fa 01 0f 85 b3 01 00 00 48 8b 44 24 10 8b 54 24 18 <89> 10 e9 15 fd ff ff 48 8b 44 24 10 8b 10 48 8b 44 24 08 48 85 c0
RSP: 002b:00007ffcb53a15d0 EFLAGS: 00010246
RAX: 0000200000002000 RBX: 0000000000000004 RCX: 0000000000000000
RDX: 0000000000000004 RSI: 0000000000000000 RDI: 000055556852e3c8
RBP: 00007ffcb53a16d8 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00007fbb473e609c
R13: 00007fbb473e6090 R14: fffffffffffffffe R15: 00007ffcb53a1720
 </TASK>
