====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.711/12546 is trying to acquire lock: ffff888060a77760 (mapping.invalidate_lock#8){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] ffff888060a77760 (mapping.invalidate_lock#8){++++}-{4:4}, at: filemap_fault+0x6e0/0x13c0 mm/filemap.c:3570 but task is already holding lock: ffff88803f7e8430 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:592 [inline] ffff88803f7e8430 (&mm->mmap_lock){++++}-{4:4}, at: __mm_populate+0x182/0x390 mm/gup.c:1942 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #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 stac arch/x86/include/asm/smap.h:-1 [inline] filldir+0x29f/0x630 fs/readdir.c:286 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#3/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#8){++++}-{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_read_fault mm/memory.c:5860 [inline] do_fault mm/memory.c:5994 [inline] do_pte_missing+0x1828/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 faultin_page mm/gup.c:1126 [inline] __get_user_pages+0x166b/0x2590 mm/gup.c:1428 populate_vma_page_range+0x2be/0x3c0 mm/gup.c:1860 __mm_populate+0x25f/0x390 mm/gup.c:1963 mm_populate include/linux/mm.h:4171 [inline] vm_mmap_pgoff+0x356/0x4e0 mm/util.c:586 ksys_mmap_pgoff+0x4a6/0x720 mm/mmap.c:606 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 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#8 --> &ni->ni_lock#3/5 --> &mm->mmap_lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(&mm->mmap_lock); lock(&ni->ni_lock#3/5); lock(&mm->mmap_lock); rlock(mapping.invalidate_lock#8); *** DEADLOCK *** 1 lock held by syz.4.711/12546: #0: ffff88803f7e8430 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock include/linux/mmap_lock.h:592 [inline] #0: ffff88803f7e8430 (&mm->mmap_lock){++++}-{4:4}, at: __mm_populate+0x182/0x390 mm/gup.c:1942 stack backtrace: CPU: 1 UID: 0 PID: 12546 Comm: syz.4.711 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/25/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_read_fault mm/memory.c:5860 [inline] do_fault mm/memory.c:5994 [inline] do_pte_missing+0x1828/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 faultin_page mm/gup.c:1126 [inline] __get_user_pages+0x166b/0x2590 mm/gup.c:1428 populate_vma_page_range+0x2be/0x3c0 mm/gup.c:1860 __mm_populate+0x25f/0x390 mm/gup.c:1963 mm_populate include/linux/mm.h:4171 [inline] vm_mmap_pgoff+0x356/0x4e0 mm/util.c:586 ksys_mmap_pgoff+0x4a6/0x720 mm/mmap.c:606 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 RIP: 0033:0x7fa3f717de59 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fa3f53b5028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007fa3f7406090 RCX: 00007fa3f717de59 RDX: 00000000027fffff RSI: 0000000000600000 RDI: 0000200000000000 RBP: 00007fa3f7213e6f R08: 0000000000000004 R09: 0000000000000000 R10: 0000000004012011 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fa3f7406128 R14: 00007fa3f7406090 R15: 00007ffda6b10d18