======================================================
WARNING: possible circular locking dependency detected
6.6.0-rc4-syzkaller-00029-gcbf3a2cb156a #0 Not tainted
------------------------------------------------------
syz-executor139/21695 is trying to acquire lock:
ffff88807e153120 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xa5/0x120 mm/memory.c:5896

but task is already holding lock:
ffff888077e73580 (&indx->run_lock){.+.+}-{3:3}, at: ni_fiemap+0x373/0x1230 fs/ntfs3/frecord.c:1961

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&indx->run_lock){.+.+}-{3:3}:
       down_read+0xb1/0xa40 kernel/locking/rwsem.c:1520
       ni_fiemap+0x373/0x1230 fs/ntfs3/frecord.c:1961
       ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1163
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x19ea/0x2b40 fs/ioctl.c:811
       __do_sys_ioctl fs/ioctl.c:869 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #1 (&ni->ni_lock#2/4){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
       attr_data_get_block+0x46d/0x2da0 fs/ntfs3/attrib.c:918
       ntfs_file_mmap+0x453/0x7a0 fs/ntfs3/file.c:291
       call_mmap include/linux/fs.h:1961 [inline]
       mmap_region+0xfd0/0x2280 mm/mmap.c:2754
       do_mmap+0x8d3/0xfa0 mm/mmap.c:1354
       vm_mmap_pgoff+0x1dc/0x410 mm/util.c:546
       ksys_mmap_pgoff+0x4ff/0x6d0 mm/mmap.c:1400
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3868 [inline]
       __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136
       lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753
       __might_fault+0xc1/0x120 mm/memory.c:5896
       _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:191 [inline]
       fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145
       ni_fiemap+0xa5e/0x1230 fs/ntfs3/frecord.c:2065
       ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1163
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x19ea/0x2b40 fs/ioctl.c:811
       __do_sys_ioctl fs/ioctl.c:869 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &ni->ni_lock#2/4 --> &indx->run_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  rlock(&indx->run_lock);
                               lock(&ni->ni_lock#2/4);
                               lock(&indx->run_lock);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

2 locks held by syz-executor139/21695:
 #0: ffff888077e734a0 (&ni->ni_lock#2/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
 #0: ffff888077e734a0 (&ni->ni_lock#2/4){+.+.}-{3:3}, at: ntfs_fiemap+0xff/0x180 fs/ntfs3/file.c:1161
 #1: ffff888077e73580 (&indx->run_lock){.+.+}-{3:3}, at: ni_fiemap+0x373/0x1230 fs/ntfs3/frecord.c:1961

stack backtrace:
CPU: 0 PID: 21695 Comm: syz-executor139 Not tainted 6.6.0-rc4-syzkaller-00029-gcbf3a2cb156a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x375/0x4a0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3868 [inline]
 __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136
 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753
 __might_fault+0xc1/0x120 mm/memory.c:5896
 _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
 copy_to_user include/linux/uaccess.h:191 [inline]
 fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145
 ni_fiemap+0xa5e/0x1230 fs/ntfs3/frecord.c:2065
 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1163
 ioctl_fiemap fs/ioctl.c:220 [inline]
 do_vfs_ioctl+0x19ea/0x2b40 fs/ioctl.c:811
 __do_sys_ioctl fs/ioctl.c:869 [inline]
 __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7efd4230e559
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 21 1f 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efd3989e168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007efd423ae6f8 RCX: 00007efd4230e559
RDX: 0000000020000400 RSI: 00000000c020660b RDI: 0000000000000005
RBP: 00007efd423ae6f0 R08: 00007efd3989e6c0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007efd423ae6fc
R13: 000000000000006e R14: 00007ffd2963d250 R15: 00007ffd2963d338
 </TASK>