====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.6.696/11998 is trying to acquire lock: ffff8880661c8578 (mapping.invalidate_lock#6){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1092 [inline] ffff8880661c8578 (mapping.invalidate_lock#6){++++}-{4:4}, at: filemap_fault+0x5cc/0x12b0 mm/filemap.c:3537 but task is already holding lock: ffff88803ab09588 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1a7/0x4a0 mm/mmap_lock.c:259 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (vm_lock){++++}-{0:0}: __vma_enter_locked+0x23a/0x730 mm/mmap_lock.c:72 __vma_start_write+0x23/0x140 mm/mmap_lock.c:104 vma_start_write include/linux/mmap_lock.h:213 [inline] mprotect_fixup+0x5af/0xa30 mm/mprotect.c:768 setup_arg_pages+0x52a/0xa90 fs/exec.c:670 load_elf_binary+0xbad/0x2750 fs/binfmt_elf.c:1028 search_binary_handler fs/exec.c:1669 [inline] exec_binprm fs/exec.c:1701 [inline] bprm_execve+0x92e/0x1400 fs/exec.c:1753 kernel_execve+0x8f0/0x9f0 fs/exec.c:1919 try_to_run_init_process+0x13/0x60 init/main.c:1506 kernel_init+0xad/0x1d0 init/main.c:1634 ret_from_fork+0x599/0xb30 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246 -> #2 (&mm->mmap_lock){++++}-{4:4}: __might_fault+0xcc/0x130 mm/memory.c:7174 _inline_copy_to_user include/linux/uaccess.h:201 [inline] _copy_to_user+0x2c/0xb0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:236 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:144 ni_fiemap+0x391/0xbf0 fs/ntfs3/frecord.c:1898 ntfs_fiemap+0x11d/0x1a0 fs/ntfs3/file.c:1419 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0x1188/0x1440 fs/ioctl.c:531 __do_sys_ioctl fs/ioctl.c:595 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&ni->ni_lock#2/5){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:533 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552 ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline] ntfs_fallocate+0x580/0x10b0 fs/ntfs3/file.c:634 vfs_fallocate+0x672/0x7f0 fs/open.c:339 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x61d/0x780 fs/ioctl.c:-1 do_vfs_ioctl+0xb36/0x1440 fs/ioctl.c:576 __do_sys_ioctl fs/ioctl.c:595 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (mapping.invalidate_lock#6){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:1092 [inline] filemap_fault+0x5cc/0x12b0 mm/filemap.c:3537 __do_fault+0x138/0x390 mm/memory.c:5320 do_shared_fault mm/memory.c:5819 [inline] do_fault mm/memory.c:5893 [inline] do_pte_missing+0x69d/0x27a0 mm/memory.c:4401 handle_pte_fault mm/memory.c:6273 [inline] __handle_mm_fault mm/memory.c:6411 [inline] handle_mm_fault+0xcc1/0x1330 mm/memory.c:6580 do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x82/0x100 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#6 --> &mm->mmap_lock --> vm_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(vm_lock); lock(&mm->mmap_lock); lock(vm_lock); rlock(mapping.invalidate_lock#6); *** DEADLOCK *** 1 lock held by syz.6.696/11998: #0: ffff88803ab09588 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1a7/0x4a0 mm/mmap_lock.c:259 stack backtrace: CPU: 1 UID: 0 PID: 11998 Comm: syz.6.696 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:1092 [inline] filemap_fault+0x5cc/0x12b0 mm/filemap.c:3537 __do_fault+0x138/0x390 mm/memory.c:5320 do_shared_fault mm/memory.c:5819 [inline] do_fault mm/memory.c:5893 [inline] do_pte_missing+0x69d/0x27a0 mm/memory.c:4401 handle_pte_fault mm/memory.c:6273 [inline] __handle_mm_fault mm/memory.c:6411 [inline] handle_mm_fault+0xcc1/0x1330 mm/memory.c:6580 do_user_addr_fault+0xa7c/0x1380 arch/x86/mm/fault.c:1336 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x82/0x100 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 RIP: 0033:0x7f6aeaa57398 Code: fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 66 0f 1f 84 00 00 00 00 00 48 8b 4c 16 f8 48 8b 36 <48> 89 37 48 89 4c 17 f8 c3 c5 fe 6f 54 16 e0 c5 fe 6f 5c 16 c0 c5 RSP: 002b:00007ffe8a3cdcf8 EFLAGS: 00010246 RAX: 0000200000000300 RBX: 0000000000000004 RCX: 0031656c69662f2e RDX: 0000000000000008 RSI: 0031656c69662f2e RDI: 0000200000000300 RBP: 00007f6aeace7da0 R08: 0000001b32920000 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000009 R12: 00007f6aeace5fac R13: 00007ffe8a3cddf0 R14: fffffffffffffffe R15: 00007ffe8a3cde10