======================================================
WARNING: possible circular locking dependency detected
6.15.0-rc5-syzkaller-00300-g3ce9925823c7 #0 Not tainted
------------------------------------------------------
syz.2.1452/10832 is trying to acquire lock:
ffff888079081fe0 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault mm/memory.c:7151 [inline]
ffff888079081fe0 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault+0xe3/0x190 mm/memory.c:7145

but task is already holding lock:
ffff888056bca5b8 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
ffff888056bca5b8 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ntfs_fiemap+0xb5/0x110 fs/ntfs3/file.c:1378

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->ni_lock#3/5){+.+.}-{4:4}:
       __mutex_lock_common kernel/locking/mutex.c:601 [inline]
       __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:746
       ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
       attr_data_get_block+0x303/0x1d10 fs/ntfs3/attrib.c:918
       ntfs_file_mmap+0x575/0x780 fs/ntfs3/file.c:389
       call_mmap include/linux/fs.h:2243 [inline]
       mmap_file mm/internal.h:167 [inline]
       __mmap_new_file_vma mm/vma.c:2353 [inline]
       __mmap_new_vma mm/vma.c:2417 [inline]
       __mmap_region+0x1488/0x27c0 mm/vma.c:2519
       mmap_region+0x32b/0x3f0 mm/vma.c:2597
       do_mmap+0xd8e/0x11b0 mm/mmap.c:561
       vm_mmap_pgoff+0x281/0x450 mm/util.c:579
       ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:607
       __do_sys_mmap arch/x86/kernel/sys_x86_64.c:89 [inline]
       __se_sys_mmap arch/x86/kernel/sys_x86_64.c:82 [inline]
       __x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:82
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&mm->mmap_lock){++++}-{4:4}:
       check_prev_add kernel/locking/lockdep.c:3166 [inline]
       check_prevs_add kernel/locking/lockdep.c:3285 [inline]
       validate_chain kernel/locking/lockdep.c:3909 [inline]
       __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
       lock_acquire kernel/locking/lockdep.c:5866 [inline]
       lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
       __might_fault mm/memory.c:7151 [inline]
       __might_fault+0x113/0x190 mm/memory.c:7145
       _inline_copy_to_user include/linux/uaccess.h:192 [inline]
       _copy_to_user+0x2d/0xd0 lib/usercopy.c:26
       copy_to_user include/linux/uaccess.h:225 [inline]
       fiemap_fill_next_extent+0x239/0x390 fs/ioctl.c:145
       ni_fiemap+0x40d/0xbf0 fs/ntfs3/frecord.c:2007
       ntfs_fiemap+0xc8/0x110 fs/ntfs3/file.c:1380
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x404/0x1990 fs/ioctl.c:840
       __do_sys_ioctl fs/ioctl.c:904 [inline]
       __se_sys_ioctl fs/ioctl.c:892 [inline]
       __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ni->ni_lock#3/5);
                               lock(&mm->mmap_lock);
                               lock(&ni->ni_lock#3/5);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.2.1452/10832:
 #0: ffff888056bca5b8 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1105 [inline]
 #0: ffff888056bca5b8 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ntfs_fiemap+0xb5/0x110 fs/ntfs3/file.c:1378

stack backtrace:
CPU: 0 UID: 0 PID: 10832 Comm: syz.2.1452 Not tainted 6.15.0-rc5-syzkaller-00300-g3ce9925823c7 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120
 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2079
 check_noncircular+0x14c/0x170 kernel/locking/lockdep.c:2211
 check_prev_add kernel/locking/lockdep.c:3166 [inline]
 check_prevs_add kernel/locking/lockdep.c:3285 [inline]
 validate_chain kernel/locking/lockdep.c:3909 [inline]
 __lock_acquire+0x1173/0x1ba0 kernel/locking/lockdep.c:5235
 lock_acquire kernel/locking/lockdep.c:5866 [inline]
 lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5823
 __might_fault mm/memory.c:7151 [inline]
 __might_fault+0x113/0x190 mm/memory.c:7145
 _inline_copy_to_user include/linux/uaccess.h:192 [inline]
 _copy_to_user+0x2d/0xd0 lib/usercopy.c:26
 copy_to_user include/linux/uaccess.h:225 [inline]
 fiemap_fill_next_extent+0x239/0x390 fs/ioctl.c:145
 ni_fiemap+0x40d/0xbf0 fs/ntfs3/frecord.c:2007
 ntfs_fiemap+0xc8/0x110 fs/ntfs3/file.c:1380
 ioctl_fiemap fs/ioctl.c:220 [inline]
 do_vfs_ioctl+0x404/0x1990 fs/ioctl.c:840
 __do_sys_ioctl fs/ioctl.c:904 [inline]
 __se_sys_ioctl fs/ioctl.c:892 [inline]
 __x64_sys_ioctl+0x11d/0x200 fs/ioctl.c:892
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xcd/0x260 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f39b838e969
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:00007f39b91ab038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f39b85b5fa0 RCX: 00007f39b838e969
RDX: 0000200000000080 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f39b8410ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f39b85b5fa0 R15: 00007ffca2a379b8
 </TASK>