======================================================
WARNING: possible circular locking dependency detected
6.11.0-rc5-syzkaller-00081-gd5d547aa7b51 #0 Not tainted
------------------------------------------------------
syz.3.574/7722 is trying to acquire lock:
ffff888012389e18 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault mm/memory.c:6387 [inline]
ffff888012389e18 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xe3/0x190 mm/memory.c:6380

but task is already holding lock:
ffff88807a5b7680 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
ffff88807a5b7680 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_fiemap+0xb6/0x120 fs/ntfs3/file.c:1277

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->ni_lock/4){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:608 [inline]
       __mutex_lock+0x175/0x9c0 kernel/locking/mutex.c:752
       ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
       attr_data_get_block+0x307/0x1d40 fs/ntfs3/attrib.c:917
       ntfs_file_mmap+0x57d/0x780 fs/ntfs3/file.c:360
       call_mmap include/linux/fs.h:2130 [inline]
       mmap_region+0x75a/0x2760 mm/mmap.c:2957
       do_mmap+0xbfb/0xfb0 mm/mmap.c:1468
       vm_mmap_pgoff+0x1ba/0x360 mm/util.c:588
       ksys_mmap_pgoff+0x332/0x5d0 mm/mmap.c:1514
       __do_sys_mmap arch/x86/kernel/sys_x86_64.c:86 [inline]
       __se_sys_mmap arch/x86/kernel/sys_x86_64.c:79 [inline]
       __x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:79
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       entry_SYSCALL_64_after_hwframe+0x77/0x7f

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3133 [inline]
       check_prevs_add kernel/locking/lockdep.c:3252 [inline]
       validate_chain kernel/locking/lockdep.c:3868 [inline]
       __lock_acquire+0x24ed/0x3cb0 kernel/locking/lockdep.c:5142
       lock_acquire kernel/locking/lockdep.c:5759 [inline]
       lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5724
       __might_fault mm/memory.c:6387 [inline]
       __might_fault+0x11b/0x190 mm/memory.c:6380
       _inline_copy_to_user include/linux/uaccess.h:176 [inline]
       _copy_to_user+0x2b/0xc0 lib/usercopy.c:26
       copy_to_user include/linux/uaccess.h:209 [inline]
       ni_fiemap+0xc4f/0xe50 fs/ntfs3/frecord.c:2140
       ntfs_fiemap+0xc9/0x120 fs/ntfs3/file.c:1279
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x407/0x1ad0 fs/ioctl.c:841
       __do_sys_ioctl fs/ioctl.c:905 [inline]
       __se_sys_ioctl fs/ioctl.c:893 [inline]
       __x64_sys_ioctl+0x116/0x220 fs/ioctl.c:893
       do_syscall_x64 arch/x86/entry/common.c:52 [inline]
       do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
       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/4);
                               lock(&mm->mmap_lock);
                               lock(&ni->ni_lock/4);
  rlock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.3.574/7722:
 #0: ffff88807a5b7680 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1110 [inline]
 #0: ffff88807a5b7680 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_fiemap+0xb6/0x120 fs/ntfs3/file.c:1277

stack backtrace:
CPU: 0 UID: 0 PID: 7722 Comm: syz.3.574 Not tainted 6.11.0-rc5-syzkaller-00081-gd5d547aa7b51 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:93 [inline]
 dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:119
 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2186
 check_prev_add kernel/locking/lockdep.c:3133 [inline]
 check_prevs_add kernel/locking/lockdep.c:3252 [inline]
 validate_chain kernel/locking/lockdep.c:3868 [inline]
 __lock_acquire+0x24ed/0x3cb0 kernel/locking/lockdep.c:5142
 lock_acquire kernel/locking/lockdep.c:5759 [inline]
 lock_acquire+0x1b1/0x560 kernel/locking/lockdep.c:5724
 __might_fault mm/memory.c:6387 [inline]
 __might_fault+0x11b/0x190 mm/memory.c:6380
 _inline_copy_to_user include/linux/uaccess.h:176 [inline]
 _copy_to_user+0x2b/0xc0 lib/usercopy.c:26
 copy_to_user include/linux/uaccess.h:209 [inline]
 ni_fiemap+0xc4f/0xe50 fs/ntfs3/frecord.c:2140
 ntfs_fiemap+0xc9/0x120 fs/ntfs3/file.c:1279
 ioctl_fiemap fs/ioctl.c:220 [inline]
 do_vfs_ioctl+0x407/0x1ad0 fs/ioctl.c:841
 __do_sys_ioctl fs/ioctl.c:905 [inline]
 __se_sys_ioctl fs/ioctl.c:893 [inline]
 __x64_sys_ioctl+0x116/0x220 fs/ioctl.c:893
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2894f79ef9
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:00007f2895e07038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f2895115f80 RCX: 00007f2894f79ef9
RDX: 0000000020000040 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f2894fe793e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2895115f80 R15: 00007fff9acdc558
 </TASK>