======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.4.2244/15339 is trying to acquire lock:
ffff88804ec36520 (mapping.invalidate_lock#11){++++}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
ffff88804ec36520 (mapping.invalidate_lock#11){++++}-{3:3}, at: filemap_fault+0x53c/0x1670 mm/filemap.c:3220

but task is already holding lock:
ffff88802ffdf1d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock_killable+0x1d/0x60 include/linux/mmap_lock.h:126

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (&mm->mmap_lock){++++}-{3:3}:
       __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:1173
       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

-> #1 (&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_fallocate+0x71d/0xf20 fs/ntfs3/file.c:570
       vfs_fallocate+0x584/0x6f0 fs/open.c:323
       ksys_fallocate fs/open.c:346 [inline]
       __do_sys_fallocate fs/open.c:354 [inline]
       __se_sys_fallocate fs/open.c:352 [inline]
       __x64_sys_fallocate+0xbd/0x100 fs/open.c:352
       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 (mapping.invalidate_lock#11){++++}-{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
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
       filemap_fault+0x53c/0x1670 mm/filemap.c:3220
       __do_fault+0x13b/0x4e0 mm/memory.c:4280
       do_cow_fault mm/memory.c:4661 [inline]
       do_fault mm/memory.c:4762 [inline]
       handle_pte_fault mm/memory.c:5031 [inline]
       __handle_mm_fault mm/memory.c:5173 [inline]
       handle_mm_fault+0x23b6/0x3e70 mm/memory.c:5294
       do_user_addr_fault+0x51f/0xb10 arch/x86/mm/fault.c:1340
       handle_page_fault arch/x86/mm/fault.c:1431 [inline]
       exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1487
       asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608

other info that might help us debug this:

Chain exists of:
  mapping.invalidate_lock#11 --> &ni->ni_lock/5 --> &mm->mmap_lock

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&mm->mmap_lock);
                               lock(&ni->ni_lock/5);
                               lock(&mm->mmap_lock);
  lock(mapping.invalidate_lock#11);

 *** DEADLOCK ***

1 lock held by syz.4.2244/15339:
 #0: ffff88802ffdf1d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_read_lock_killable+0x1d/0x60 include/linux/mmap_lock.h:126

stack backtrace:
CPU: 0 PID: 15339 Comm: syz.4.2244 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/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
 down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
 filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
 filemap_fault+0x53c/0x1670 mm/filemap.c:3220
 __do_fault+0x13b/0x4e0 mm/memory.c:4280
 do_cow_fault mm/memory.c:4661 [inline]
 do_fault mm/memory.c:4762 [inline]
 handle_pte_fault mm/memory.c:5031 [inline]
 __handle_mm_fault mm/memory.c:5173 [inline]
 handle_mm_fault+0x23b6/0x3e70 mm/memory.c:5294
 do_user_addr_fault+0x51f/0xb10 arch/x86/mm/fault.c:1340
 handle_page_fault arch/x86/mm/fault.c:1431 [inline]
 exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1487
 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608
RIP: 0033:0x7ff0c8c551b3
Code: 48 85 c0 74 1b 48 83 f8 01 0f 85 3b 03 00 00 0f b7 44 24 18 66 c1 c0 08 0f b7 c0 48 89 44 24 18 48 8b 44 24 10 0f b7 54 24 18 <66> 89 10 e9 82 fe ff ff 48 83 3c 24 08 0f 85 a1 02 00 00 48 8b 44
RSP: 002b:00007ffee0204590 EFLAGS: 00010246
RAX: 0000200000000000 RBX: 0000000000000002 RCX: 0000000000000000
RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000555580e903c8
RBP: 00007ffee0204698 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 00007ff0c8fe609c
R13: 00007ffee02046c0 R14: fffffffffffffffe R15: 00007ffee02046e0
 </TASK>