======================================================
WARNING: possible circular locking dependency detected
6.1.147-syzkaller #0 Not tainted
------------------------------------------------------
syz.4.186/4912 is trying to acquire lock:
ffff8880769108d8 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xa6/0x120 mm/memory.c:5852

but task is already holding lock:
ffff88805c8ad980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ffff88805c8ad980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fiemap+0xc4/0x130 fs/ntfs3/file.c:1168

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&ni->ni_lock/5){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
       ntfs_set_size+0x12d/0x1f0 fs/ntfs3/inode.c:843
       ntfs_extend+0x15c/0x510 fs/ntfs3/file.c:350
       ntfs3_setattr+0x2fa/0xc00 fs/ntfs3/file.c:709
       notify_change+0xc74/0xf40 fs/attr.c:499
       do_truncate+0x197/0x220 fs/open.c:65
       vfs_truncate+0x262/0x2f0 fs/open.c:111
       do_sys_truncate+0xdc/0x190 fs/open.c:134
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #1 (&sb->s_type->i_mutex_key#29){+.+.}-{3:3}:
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:758 [inline]
       ntfs_file_mmap+0x4de/0x6a0 fs/ntfs3/file.c:320
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_file+0x5d/0xb0 mm/util.c:1109
       __mmap_region mm/mmap.c:2768 [inline]
       mmap_region+0xf78/0x1d30 mm/mmap.c:2912
       do_mmap+0x894/0xf30 mm/mmap.c:1432
       vm_mmap_pgoff+0x1b2/0x2b0 mm/util.c:520
       ksys_mmap_pgoff+0x516/0x6f0 mm/mmap.c:1478
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
       lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
       __might_fault+0xc2/0x120 mm/memory.c:5852
       _copy_to_user+0x27/0x130 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:169 [inline]
       ni_fiemap+0x4ec/0x1300 fs/ntfs3/frecord.c:2140
       ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1170
       ioctl_fiemap fs/ioctl.c:219 [inline]
       do_vfs_ioctl+0x1425/0x1d10 fs/ioctl.c:810
       __do_sys_ioctl fs/ioctl.c:868 [inline]
       __se_sys_ioctl+0x83/0x170 fs/ioctl.c:856
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

Chain exists of:
  &mm->mmap_lock --> &sb->s_type->i_mutex_key#29 --> &ni->ni_lock/5

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ni->ni_lock/5);
                               lock(&sb->s_type->i_mutex_key#29);
                               lock(&ni->ni_lock/5);
  lock(&mm->mmap_lock);

 *** DEADLOCK ***

1 lock held by syz.4.186/4912:
 #0: ffff88805c8ad980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
 #0: ffff88805c8ad980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fiemap+0xc4/0x130 fs/ntfs3/file.c:1168

stack backtrace:
CPU: 1 PID: 4912 Comm: syz.4.186 Not tainted 6.1.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
 check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
 __might_fault+0xc2/0x120 mm/memory.c:5852
 _copy_to_user+0x27/0x130 lib/usercopy.c:36
 copy_to_user include/linux/uaccess.h:169 [inline]
 ni_fiemap+0x4ec/0x1300 fs/ntfs3/frecord.c:2140
 ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1170
 ioctl_fiemap fs/ioctl.c:219 [inline]
 do_vfs_ioctl+0x1425/0x1d10 fs/ioctl.c:810
 __do_sys_ioctl fs/ioctl.c:868 [inline]
 __se_sys_ioctl+0x83/0x170 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f5cf038eb69
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:00007f5cf11c3038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f5cf05b5fa0 RCX: 00007f5cf038eb69
RDX: 0000200000000400 RSI: 00000000c020660b RDI: 0000000000000004
RBP: 00007f5cf0411df1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f5cf05b5fa0 R15: 00007ffe8afd2218
 </TASK>