ntfs3(loop8): Different NTFS sector size (2048) and media sector size (512). ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.8.1036/23847 is trying to acquire lock: ffff888068f3f8c8 (mapping.invalidate_lock#10){++++}-{4:4}, at: filemap_invalidate_lock_shared include/linux/fs.h:1093 [inline] ffff888068f3f8c8 (mapping.invalidate_lock#10){++++}-{4:4}, at: filemap_fault+0x66f/0x12f0 mm/filemap.c:3537 but task is already holding lock: ffff88802493aa88 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1d1/0x500 mm/mmap_lock.c:259 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (vm_lock){++++}-{0:0}: __vma_enter_locked+0x243/0x710 mm/mmap_lock.c:72 __vma_start_write+0x23/0x140 mm/mmap_lock.c:104 vma_start_write include/linux/mmap_lock.h:213 [inline] mprotect_fixup+0x5e1/0xa50 mm/mprotect.c:768 setup_arg_pages+0x565/0xae0 fs/exec.c:670 load_elf_binary+0xc67/0x29b0 fs/binfmt_elf.c:1028 search_binary_handler fs/exec.c:1664 [inline] exec_binprm fs/exec.c:1696 [inline] bprm_execve+0x93d/0x1400 fs/exec.c:1748 kernel_execve+0x844/0x930 fs/exec.c:1892 try_to_run_init_process+0x13/0x60 init/main.c:1506 kernel_init+0xad/0x1d0 init/main.c:1634 ret_from_fork+0x51e/0xb90 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}: __might_fault+0xcb/0x130 mm/memory.c:7177 _inline_copy_to_user include/linux/uaccess.h:201 [inline] _copy_to_user+0x2c/0xb0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:236 [inline] fiemap_fill_next_extent+0x1dd/0x3c0 fs/ioctl.c:144 ni_fiemap+0x9a5/0xca0 fs/ntfs3/frecord.c:2009 ntfs_fiemap+0x11d/0x1a0 fs/ntfs3/file.c:1420 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0x126f/0x1540 fs/ioctl.c:531 __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+0x14d/0xf80 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:533 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:552 ni_lock fs/ntfs3/ntfs_fs.h:1127 [inline] ntfs_fallocate+0x5a6/0x1140 fs/ntfs3/file.c:635 vfs_fallocate+0x672/0x7f0 fs/open.c:340 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x64b/0x870 fs/ioctl.c:332 do_vfs_ioctl+0xc29/0x1540 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+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (mapping.invalidate_lock#10){++++}-{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+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:1093 [inline] filemap_fault+0x66f/0x12f0 mm/filemap.c:3537 __do_fault+0x138/0x390 mm/memory.c:5323 do_read_fault mm/memory.c:5758 [inline] do_fault mm/memory.c:5892 [inline] do_pte_missing+0x18d3/0x2e60 mm/memory.c:4404 handle_pte_fault mm/memory.c:6276 [inline] __handle_mm_fault mm/memory.c:6414 [inline] handle_mm_fault+0xd0a/0x13c0 mm/memory.c:6583 do_user_addr_fault+0xa73/0x1360 arch/x86/mm/fault.c:1334 handle_page_fault arch/x86/mm/fault.c:1474 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#10 --> &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#10); *** DEADLOCK *** 1 lock held by syz.8.1036/23847: #0: ffff88802493aa88 (vm_lock){++++}-{0:0}, at: lock_vma_under_rcu+0x1d1/0x500 mm/mmap_lock.c:259 stack backtrace: CPU: 1 UID: 0 PID: 23847 Comm: syz.8.1036 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/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+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:1093 [inline] filemap_fault+0x66f/0x12f0 mm/filemap.c:3537 __do_fault+0x138/0x390 mm/memory.c:5323 do_read_fault mm/memory.c:5758 [inline] do_fault mm/memory.c:5892 [inline] do_pte_missing+0x18d3/0x2e60 mm/memory.c:4404 handle_pte_fault mm/memory.c:6276 [inline] __handle_mm_fault mm/memory.c:6414 [inline] handle_mm_fault+0xd0a/0x13c0 mm/memory.c:6583 do_user_addr_fault+0xa73/0x1360 arch/x86/mm/fault.c:1334 handle_page_fault arch/x86/mm/fault.c:1474 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1527 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:618 RIP: 0033:0x7f7f7d54b439 Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 27 01 00 00 fd 74 0f c5 fd d7 c1 85 c0 74 5b f3 0f bc c0 e9 30 01 00 00 66 RSP: 002b:00007f7f7b7bd8a8 EFLAGS: 00010287 RAX: 0000000000000d40 RBX: 00007f7f7b7bdde0 RCX: 2f666c65732f636f RDX: 0000200000001d40 RSI: 00007f7f7d62c9c0 RDI: 0000200000001d40 RBP: 0000200000001d40 R08: 00007f7f7b7be010 R09: 00000000ffffffff R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 R13: 0000000000000073 R14: 00007f7f7d601e03 R15: 00007f7f7b7bdea0