====================================================== WARNING: possible circular locking dependency detected 6.1.123-syzkaller #0 Not tainted ------------------------------------------------------ syz.7.890/8563 is trying to acquire lock: ffff88807206e0e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] ffff88807206e0e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_read_folio+0x18f/0x210 fs/ntfs3/inode.c:727 but task is already holding lock: ffff88807206e520 (mapping.invalidate_lock#6){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:813 [inline] ffff88807206e520 (mapping.invalidate_lock#6){.+.+}-{3:3}, at: filemap_fault+0xb34/0x17e0 mm/filemap.c:3234 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (mapping.invalidate_lock#6){.+.+}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 down_read+0xad/0xa30 kernel/locking/rwsem.c:1520 filemap_invalidate_lock_shared include/linux/fs.h:813 [inline] filemap_fault+0x640/0x17e0 mm/filemap.c:3219 __do_fault+0x136/0x4f0 mm/memory.c:4278 do_read_fault mm/memory.c:4629 [inline] do_fault mm/memory.c:4758 [inline] handle_pte_fault mm/memory.c:5029 [inline] __handle_mm_fault mm/memory.c:5171 [inline] handle_mm_fault+0x3410/0x5340 mm/memory.c:5292 faultin_page mm/gup.c:1009 [inline] __get_user_pages+0x4f3/0x1190 mm/gup.c:1233 populate_vma_page_range+0x217/0x2b0 mm/gup.c:1590 __mm_populate+0x275/0x440 mm/gup.c:1704 mm_populate include/linux/mm.h:2801 [inline] vm_mmap_pgoff+0x22b/0x2d0 mm/util.c:525 ksys_mmap_pgoff+0x4f5/0x6d0 mm/mmap.c:1470 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #1 (&mm->mmap_lock){++++}-{3:3}: lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __might_fault+0xbd/0x110 mm/memory.c:5851 _copy_to_user+0x26/0x130 lib/usercopy.c:36 copy_to_user include/linux/uaccess.h:169 [inline] ni_fiemap+0x1672/0x18a0 fs/ntfs3/frecord.c:2140 ntfs_fiemap+0x12e/0x170 fs/ntfs3/file.c:1254 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0x18e9/0x2a90 fs/ioctl.c:810 __do_sys_ioctl fs/ioctl.c:868 [inline] __se_sys_ioctl+0x81/0x160 fs/ioctl.c:856 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&ni->ni_lock/5){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] ntfs_read_folio+0x18f/0x210 fs/ntfs3/inode.c:727 filemap_read_folio+0x199/0x780 mm/filemap.c:2489 filemap_fault+0xf6e/0x17e0 mm/filemap.c:3312 __do_fault+0x136/0x4f0 mm/memory.c:4278 do_read_fault mm/memory.c:4629 [inline] do_fault mm/memory.c:4758 [inline] handle_pte_fault mm/memory.c:5029 [inline] __handle_mm_fault mm/memory.c:5171 [inline] handle_mm_fault+0x3410/0x5340 mm/memory.c:5292 do_user_addr_fault arch/x86/mm/fault.c:1340 [inline] handle_page_fault arch/x86/mm/fault.c:1431 [inline] exc_page_fault+0x26f/0x620 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: &ni->ni_lock/5 --> &mm->mmap_lock --> mapping.invalidate_lock#6 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#6); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#6); lock(&ni->ni_lock/5); *** DEADLOCK *** 1 lock held by syz.7.890/8563: #0: ffff88807206e520 (mapping.invalidate_lock#6){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:813 [inline] #0: ffff88807206e520 (mapping.invalidate_lock#6){.+.+}-{3:3}, at: filemap_fault+0xb34/0x17e0 mm/filemap.c:3234 stack backtrace: CPU: 0 PID: 8563 Comm: syz.7.890 Not tainted 6.1.123-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 check_noncircular+0x2fa/0x3b0 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+0x1661/0x5950 kernel/locking/lockdep.c:3825 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x132/0xd80 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] ntfs_read_folio+0x18f/0x210 fs/ntfs3/inode.c:727 filemap_read_folio+0x199/0x780 mm/filemap.c:2489 filemap_fault+0xf6e/0x17e0 mm/filemap.c:3312 __do_fault+0x136/0x4f0 mm/memory.c:4278 do_read_fault mm/memory.c:4629 [inline] do_fault mm/memory.c:4758 [inline] handle_pte_fault mm/memory.c:5029 [inline] __handle_mm_fault mm/memory.c:5171 [inline] handle_mm_fault+0x3410/0x5340 mm/memory.c:5292 do_user_addr_fault arch/x86/mm/fault.c:1340 [inline] handle_page_fault arch/x86/mm/fault.c:1431 [inline] exc_page_fault+0x26f/0x620 arch/x86/mm/fault.c:1487 asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608 RIP: 0033:0x7fbb3844cb90 Code: 18 48 0f ca 48 89 54 24 18 48 83 f8 01 0f 85 7a 02 00 00 48 8b 44 24 10 48 8b 54 24 18 48 89 10 e9 d2 fd ff ff 48 8b 44 24 10 <0f> b7 10 48 8b 44 24 08 48 85 c0 0f 84 36 01 00 00 48 83 f8 01 0f RSP: 002b:00007fff1fef2cd0 EFLAGS: 00010202 RAX: 0000000020016e5a RBX: 000000000e000002 RCX: 0000000000000000 RDX: c7713daf7102b20e RSI: 0000000000000000 RDI: 000055555a0dd3c8 RBP: 00007fff1fef2de8 R08: 0000000000000000 R09: 000000000000000e R10: 0000000000000000 R11: 0000000000000000 R12: 000000000005f1dc R13: 00007fbb38776160 R14: 0000000000000032 R15: fffffffffffffffe