ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512). ====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc4-syzkaller-00013-g66701750d556 #0 Not tainted ------------------------------------------------------ syz.0.517/10920 is trying to acquire lock: ffff8880596793e8 (mapping.invalidate_lock#13){.+.+}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:934 [inline] ffff8880596793e8 (mapping.invalidate_lock#13){.+.+}-{4:4}, at: filemap_fault+0x546/0x1200 mm/filemap.c:3400 but task is already holding lock: ffff888037aad948 (vm_lock){++++}-{0:0}, at: do_user_addr_fault+0x2d9/0x1390 arch/x86/mm/fault.c:1327 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (vm_lock){++++}-{0:0}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __vma_enter_locked+0x182/0x380 mm/mmap_lock.c:63 __vma_start_write+0x1e/0x120 mm/mmap_lock.c:87 vma_start_write include/linux/mmap_lock.h:267 [inline] mprotect_fixup+0x571/0x9b0 mm/mprotect.c:670 setup_arg_pages+0x53a/0xaa0 fs/exec.c:667 load_elf_binary+0xb59/0x2790 fs/binfmt_elf.c:1013 search_binary_handler fs/exec.c:1665 [inline] exec_binprm fs/exec.c:1697 [inline] bprm_execve+0x999/0x1440 fs/exec.c:1749 kernel_execve+0x8f0/0x9f0 fs/exec.c:1915 try_to_run_init_process+0x13/0x60 init/main.c:1402 kernel_init+0xad/0x1d0 init/main.c:1530 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245 -> #2 (&mm->mmap_lock){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __might_fault+0xcc/0x130 mm/memory.c:6971 _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+0xda/0x130 fs/ntfs3/file.c:1290 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x16d3/0x1990 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:893 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 (&ni->ni_lock#2/5){+.+.}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x182/0xe80 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] ntfs_read_folio+0xba/0x200 fs/ntfs3/inode.c:726 filemap_read_folio+0x117/0x380 mm/filemap.c:2412 filemap_create_folio mm/filemap.c:2547 [inline] filemap_get_pages+0xd4e/0x1ea0 mm/filemap.c:2608 filemap_read+0x3f6/0x11a0 mm/filemap.c:2711 new_sync_read fs/read_write.c:491 [inline] vfs_read+0x4cd/0x980 fs/read_write.c:572 ksys_read+0x145/0x250 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 -> #0 (mapping.invalidate_lock#13){.+.+}-{4:4}: check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 filemap_invalidate_lock_shared include/linux/fs.h:934 [inline] filemap_fault+0x546/0x1200 mm/filemap.c:3400 __do_fault+0x135/0x390 mm/memory.c:5169 do_shared_fault mm/memory.c:5654 [inline] do_fault mm/memory.c:5728 [inline] do_pte_missing mm/memory.c:4251 [inline] handle_pte_fault mm/memory.c:6069 [inline] __handle_mm_fault+0x198b/0x5620 mm/memory.c:6212 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6381 do_user_addr_fault+0xa81/0x1390 arch/x86/mm/fault.c:1336 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#13 --> &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#13); *** DEADLOCK *** 1 lock held by syz.0.517/10920: #0: ffff888037aad948 (vm_lock){++++}-{0:0}, at: do_user_addr_fault+0x2d9/0x1390 arch/x86/mm/fault.c:1327 stack backtrace: CPU: 1 UID: 0 PID: 10920 Comm: syz.0.517 Not tainted 6.16.0-rc4-syzkaller-00013-g66701750d556 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 filemap_invalidate_lock_shared include/linux/fs.h:934 [inline] filemap_fault+0x546/0x1200 mm/filemap.c:3400 __do_fault+0x135/0x390 mm/memory.c:5169 do_shared_fault mm/memory.c:5654 [inline] do_fault mm/memory.c:5728 [inline] do_pte_missing mm/memory.c:4251 [inline] handle_pte_fault mm/memory.c:6069 [inline] __handle_mm_fault+0x198b/0x5620 mm/memory.c:6212 handle_mm_fault+0x2d5/0x7f0 mm/memory.c:6381 do_user_addr_fault+0xa81/0x1390 arch/x86/mm/fault.c:1336 handle_page_fault arch/x86/mm/fault.c:1476 [inline] exc_page_fault+0x76/0xf0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 RIP: 0033:0x7f2795f5666b Code: fa 10 73 2d 83 fa 08 73 46 83 fa 04 73 16 83 fa 01 7c 10 8a 0e 74 0a 0f b7 74 16 fe 66 89 74 17 fe 88 0f c3 8b 4c 16 fc 8b 36 <89> 4c 17 fc 89 37 c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 RSP: 002b:00007f2796d47028 EFLAGS: 00010246 RAX: 0000200000001114 RBX: 00007f27961b5fa0 RCX: 00000000000001ff RDX: 0000000000000004 RSI: 00000000000001ff RDI: 0000200000001114 RBP: 00007f2796010b39 R08: 0000000000000004 R09: 0000000000000000 R10: 0000200000001000 R11: 0000200000000180 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f27961b5fa0 R15: 00007ffe40e3bc68