====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.996/20960 is trying to acquire lock: ffff8880626b6fc8 (mapping.invalidate_lock#6){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] ffff8880626b6fc8 (mapping.invalidate_lock#6){++++}-{4:4}, at: filemap_fault+0x6e0/0x13c0 mm/filemap.c:3570 but task is already holding lock: ffff8880354c0948 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1d1/0x500 mm/mmap_lock.c:310 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (vm_lock){++++}-{0:0}: __vma_start_exclude_readers+0x283/0x930 mm/mmap_lock.c:125 __vma_start_write+0xdc/0x290 mm/mmap_lock.c:148 vma_start_write include/linux/mmap_lock.h:303 [inline] mprotect_fixup+0x761/0xb10 mm/mprotect.c:801 setup_arg_pages+0x658/0xbd0 fs/exec.c:674 load_elf_binary+0xc85/0x2970 fs/binfmt_elf.c:1028 search_binary_handler fs/exec.c:1694 [inline] exec_binprm fs/exec.c:1726 [inline] bprm_execve+0x926/0x14b0 fs/exec.c:1778 kernel_execve+0x8c3/0x9c0 fs/exec.c:1922 try_to_run_init_process+0x13/0x60 init/main.c:1476 kernel_init+0xad/0x1d0 init/main.c:1604 ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 -> #2 (&mm->mmap_lock){++++}-{4:4}: down_read_killable+0xa4/0x220 kernel/locking/rwsem.c:1599 mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:601 get_mmap_lock_carefully mm/mmap_lock.c:450 [inline] lock_mm_and_find_vma+0x2d6/0x340 mm/mmap_lock.c:501 do_user_addr_fault+0x341/0x1340 arch/x86/mm/fault.c:1366 handle_page_fault arch/x86/mm/fault.c:1483 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 filldir+0x2bd/0x630 fs/readdir.c:-1 dir_emit include/linux/fs.h:3587 [inline] ntfs_dir_emit fs/ntfs3/dir.c:346 [inline] ntfs_read_hdr+0x8a4/0xc10 fs/ntfs3/dir.c:387 ntfs_readdir+0x9ea/0xec0 fs/ntfs3/dir.c:547 iterate_dir+0x2f1/0x4e0 fs/readdir.c:110 __do_sys_getdents fs/readdir.c:319 [inline] __se_sys_getdents+0xf1/0x270 fs/readdir.c:304 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&ni->ni_lock/5){+.+.}-{4:4}: __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578 ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline] ntfs_fallocate+0x54d/0xf70 fs/ntfs3/file.c:535 vfs_fallocate+0x663/0x7f0 fs/open.c:338 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x5db/0x7e0 fs/ioctl.c:332 do_vfs_ioctl+0xc2a/0x1550 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+0x174/0x580 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+0x1520/0x2ce0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1574 filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] filemap_fault+0x6e0/0x13c0 mm/filemap.c:3570 __do_fault+0x138/0x2a0 mm/memory.c:5425 do_cow_fault mm/memory.c:5890 [inline] do_fault mm/memory.c:5996 [inline] do_pte_missing+0xfe7/0x28f0 mm/memory.c:4566 handle_pte_fault mm/memory.c:6379 [inline] __handle_mm_fault mm/memory.c:6517 [inline] handle_mm_fault+0xd28/0x13f0 mm/memory.c:6686 do_user_addr_fault+0xa4d/0x1340 arch/x86/mm/fault.c:1343 handle_page_fault arch/x86/mm/fault.c:1483 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 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.1.996/20960: #0: ffff8880354c0948 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1d1/0x500 mm/mmap_lock.c:310 stack backtrace: CPU: 0 UID: 0 PID: 20960 Comm: syz.1.996 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/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+0x1520/0x2ce0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1574 filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] filemap_fault+0x6e0/0x13c0 mm/filemap.c:3570 __do_fault+0x138/0x2a0 mm/memory.c:5425 do_cow_fault mm/memory.c:5890 [inline] do_fault mm/memory.c:5996 [inline] do_pte_missing+0xfe7/0x28f0 mm/memory.c:4566 handle_pte_fault mm/memory.c:6379 [inline] __handle_mm_fault mm/memory.c:6517 [inline] handle_mm_fault+0xd28/0x13f0 mm/memory.c:6686 do_user_addr_fault+0xa4d/0x1340 arch/x86/mm/fault.c:1343 handle_page_fault arch/x86/mm/fault.c:1483 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 RIP: 0033:0x7fd36512d023 Code: c5 fe 6f 5e 40 c5 fe 6f 66 60 48 83 ee 80 c5 fd 7f 0f c5 fd 7f 57 20 c5 fd 7f 5f 40 c5 fd 7f 67 60 48 83 ef 80 48 39 fa 77 cd fe 7f 6a 60 c5 fe 7f 72 40 c5 fe 7f 7a 20 c5 7e 7f 02 c5 fe 7f RSP: 002b:00007ffdb7aaed88 EFLAGS: 00010287 RAX: 0000200000000f00 RBX: 0000000000000004 RCX: 0000200000000f00 RDX: 0000200000000f81 RSI: 0000001b2f04bc93 RDI: 0000200000000fa0 RBP: fffffffffffffffe R08: 0000000000000000 R09: 0000000000000001 R10: 7ffffffffffffefe R11: 0000000000000009 R12: 00007ffdb7aaeeb0 R13: 00007fd3653e5fac R14: 0000000000190a5e R15: 00007ffdb7aaee90