======================================================
WARNING: possible circular locking dependency detected
5.15.183-syzkaller #0 Not tainted
------------------------------------------------------
syz.2.48/4624 is trying to acquire lock:
ffff88801dd0b928 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x90/0x110 mm/memory.c:5356

but task is already holding lock:
ffff888073f7e920 (&indx->run_lock){.+.+}-{3:3}, at: ni_fiemap+0x2de/0xc20 fs/ntfs3/frecord.c:1915

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&indx->run_lock){.+.+}-{3:3}:
       down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498
       indx_read+0x2b5/0xc90 fs/ntfs3/index.c:1066
       indx_find+0x4c6/0xba0 fs/ntfs3/index.c:1187
       indx_insert_entry+0x4ea/0x720 fs/ntfs3/index.c:1953
       ni_add_name+0x4b9/0x7c0 fs/ntfs3/frecord.c:2993
       ntfs_link_inode+0x315/0x3d0 fs/ntfs3/inode.c:1711
       ntfs_link+0x114/0x280 fs/ntfs3/namei.c:154
       vfs_link+0x615/0x7c0 fs/namei.c:4557
       do_linkat+0x277/0x7b0 fs/namei.c:4628
       __do_sys_link fs/namei.c:4662 [inline]
       __se_sys_link fs/namei.c:4660 [inline]
       __x64_sys_link+0x82/0x90 fs/namei.c:4660
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #1 (&ni->ni_lock/5){+.+.}-{3:3}:
       __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
       __mutex_lock kernel/locking/mutex.c:729 [inline]
       mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
       ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
       attr_data_get_block+0x2df/0x1880 fs/ntfs3/attrib.c:849
       ntfs_file_mmap+0x457/0x720 fs/ntfs3/file.c:389
       call_mmap include/linux/fs.h:2177 [inline]
       mmap_file+0x5d/0xb0 mm/util.c:1092
       __mmap_region mm/mmap.c:1784 [inline]
       mmap_region+0xd0d/0x15e0 mm/mmap.c:2921
       do_mmap+0x77a/0xdf0 mm/mmap.c:1574
       vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:551
       ksys_mmap_pgoff+0x542/0x780 mm/mmap.c:1623
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3053 [inline]
       check_prevs_add kernel/locking/lockdep.c:3172 [inline]
       validate_chain kernel/locking/lockdep.c:3788 [inline]
       __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
       lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
       __might_fault+0xb3/0x110 mm/memory.c:5357
       _copy_to_user+0x29/0x130 lib/usercopy.c:35
       copy_to_user include/linux/uaccess.h:200 [inline]
       fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144
       ni_fiemap+0x92d/0xc20 fs/ntfs3/frecord.c:2019
       ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1233
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814
       __do_sys_ioctl fs/ioctl.c:872 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x66/0xd0

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &ni->ni_lock/5 --> &indx->run_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&indx->run_lock);
                               lock(&ni->ni_lock/5);
                               lock(&indx->run_lock);
  lock(&mm->mmap_lock);

 *** DEADLOCK ***

2 locks held by syz.2.48/4624:
 #0: ffff888073f7e840 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
 #0: ffff888073f7e840 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fiemap+0xc4/0x130 fs/ntfs3/file.c:1231
 #1: ffff888073f7e920 (&indx->run_lock){.+.+}-{3:3}, at: ni_fiemap+0x2de/0xc20 fs/ntfs3/frecord.c:1915

stack backtrace:
CPU: 0 PID: 4624 Comm: syz.2.48 Not tainted 5.15.183-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2133
 check_prev_add kernel/locking/lockdep.c:3053 [inline]
 check_prevs_add kernel/locking/lockdep.c:3172 [inline]
 validate_chain kernel/locking/lockdep.c:3788 [inline]
 __lock_acquire+0x2c33/0x7c60 kernel/locking/lockdep.c:5012
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __might_fault+0xb3/0x110 mm/memory.c:5357
 _copy_to_user+0x29/0x130 lib/usercopy.c:35
 copy_to_user include/linux/uaccess.h:200 [inline]
 fiemap_fill_next_extent+0x19d/0x360 fs/ioctl.c:144
 ni_fiemap+0x92d/0xc20 fs/ntfs3/frecord.c:2019
 ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1233
 ioctl_fiemap fs/ioctl.c:219 [inline]
 do_vfs_ioctl+0x1464/0x1de0 fs/ioctl.c:814
 __do_sys_ioctl fs/ioctl.c:872 [inline]
 __se_sys_ioctl+0x83/0x170 fs/ioctl.c:860
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f2e3226e969
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:00007f2e300d6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2e32495fa0 RCX: 00007f2e3226e969
RDX: 0000200000000040 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f2e322f0ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2e32495fa0 R15: 00007fff31b99648
 </TASK>