====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.290/10092 is trying to acquire lock: ffff88804982ed70 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ffff88804982ed70 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_read_folio+0xba/0x200 fs/ntfs3/inode.c:726 but task is already holding lock: ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:935 [inline] ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_create_folio mm/filemap.c:2539 [inline] ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_get_pages+0xbe1/0x1df0 mm/filemap.c:2609 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (mapping.invalidate_lock#3){.+.+}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:935 [inline] filemap_fault+0x551/0x1210 mm/filemap.c:3433 __do_fault+0x135/0x390 mm/memory.c:5152 do_read_fault mm/memory.c:5573 [inline] do_fault mm/memory.c:5707 [inline] do_pte_missing mm/memory.c:4234 [inline] handle_pte_fault mm/memory.c:6052 [inline] __handle_mm_fault mm/memory.c:6195 [inline] handle_mm_fault+0x23c6/0x3400 mm/memory.c:6364 faultin_page mm/gup.c:1144 [inline] __get_user_pages+0x16e4/0x2b60 mm/gup.c:1446 populate_vma_page_range+0x29f/0x3a0 mm/gup.c:1880 __mm_populate+0x24c/0x380 mm/gup.c:1983 mm_populate include/linux/mm.h:3367 [inline] vm_mmap_pgoff+0x38a/0x4d0 mm/util.c:585 ksys_mmap_pgoff+0x4e9/0x720 mm/mmap.c:604 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&mm->mmap_lock){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __might_fault+0xcc/0x130 mm/memory.c:6958 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2c/0xb0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:145 ni_fiemap+0x89c/0xbf0 fs/ntfs3/frecord.c:2007 ntfs_fiemap+0x11d/0x1a0 fs/ntfs3/file.c:1326 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1185/0x1440 fs/ioctl.c:532 __do_sys_ioctl fs/ioctl.c:596 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ni->ni_lock#2/5){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ntfs_read_folio+0xba/0x200 fs/ntfs3/inode.c:726 filemap_read_folio+0x117/0x380 mm/filemap.c:2413 filemap_create_folio mm/filemap.c:2548 [inline] filemap_get_pages+0xcf8/0x1df0 mm/filemap.c:2609 filemap_read+0x3f9/0x11a0 mm/filemap.c:2712 new_sync_read fs/read_write.c:491 [inline] vfs_read+0x560/0xa30 fs/read_write.c:572 ksys_read+0x14b/0x260 fs/read_write.c:715 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 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: &ni->ni_lock#2/5 --> &mm->mmap_lock --> mapping.invalidate_lock#3 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(mapping.invalidate_lock#3); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#3); lock(&ni->ni_lock#2/5); *** DEADLOCK *** 2 locks held by syz.2.290/10092: #0: ffff8880243c4728 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x253/0x320 fs/file.c:1232 #1: ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:935 [inline] #1: ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_create_folio mm/filemap.c:2539 [inline] #1: ffff88804982f1f8 (mapping.invalidate_lock#3){.+.+}-{4:4}, at: filemap_get_pages+0xbe1/0x1df0 mm/filemap.c:2609 stack backtrace: CPU: 1 UID: 0 PID: 10092 Comm: syz.2.290 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043 check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ntfs_read_folio+0xba/0x200 fs/ntfs3/inode.c:726 filemap_read_folio+0x117/0x380 mm/filemap.c:2413 filemap_create_folio mm/filemap.c:2548 [inline] filemap_get_pages+0xcf8/0x1df0 mm/filemap.c:2609 filemap_read+0x3f9/0x11a0 mm/filemap.c:2712 new_sync_read fs/read_write.c:491 [inline] vfs_read+0x560/0xa30 fs/read_write.c:572 ksys_read+0x14b/0x260 fs/read_write.c:715 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff0b036eec9 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:00007ff0ae5d6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 00007ff0b05c5fa0 RCX: 00007ff0b036eec9 RDX: 0000000000002020 RSI: 000020000001fbc0 RDI: 0000000000000004 RBP: 00007ff0b03f1f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007ff0b05c6038 R14: 00007ff0b05c5fa0 R15: 00007fff973f12f8