====================================================== WARNING: possible circular locking dependency detected 6.12.0-syzkaller #0 Not tainted ------------------------------------------------------ syz.7.239/8027 is trying to acquire lock: ffff888011977098 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xaa/0x120 mm/memory.c:6716 but task is already holding lock: ffff8880548eef28 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ffff8880548eef28 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ntfs_fiemap+0xff/0x180 fs/ntfs3/file.c:1350 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&ni->ni_lock#3/5){+.+.}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __mutex_lock_common kernel/locking/mutex.c:608 [inline] __mutex_lock+0x136/0xd70 kernel/locking/mutex.c:752 ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] ntfs_fallocate+0x816/0x1270 fs/ntfs3/file.c:664 vfs_fallocate+0x569/0x6e0 fs/open.c:333 ksys_fallocate fs/open.c:356 [inline] __do_sys_fallocate fs/open.c:364 [inline] __se_sys_fallocate fs/open.c:362 [inline] __x64_sys_fallocate+0xbd/0x110 fs/open.c:362 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #2 (mapping.invalidate_lock#11){++++}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1524 filemap_invalidate_lock_shared include/linux/fs.h:870 [inline] filemap_fault+0x6e8/0x1950 mm/filemap.c:3331 __do_fault+0x135/0x460 mm/memory.c:4882 do_shared_fault mm/memory.c:5361 [inline] do_fault mm/memory.c:5435 [inline] do_pte_missing mm/memory.c:3965 [inline] handle_pte_fault+0x1105/0x6820 mm/memory.c:5766 __handle_mm_fault mm/memory.c:5909 [inline] handle_mm_fault+0x1053/0x1ad0 mm/memory.c:6077 do_user_addr_fault arch/x86/mm/fault.c:1338 [inline] handle_page_fault arch/x86/mm/fault.c:1481 [inline] exc_page_fault+0x459/0x8c0 arch/x86/mm/fault.c:1539 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:623 -> #1 (&vma->vm_lock->lock){++++}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 down_write+0x99/0x220 kernel/locking/rwsem.c:1577 vma_start_write include/linux/mm.h:757 [inline] vma_link+0x28c/0x500 mm/vma.c:1600 insert_vm_struct+0x2f7/0x410 mm/mmap.c:1995 __bprm_mm_init fs/exec.c:289 [inline] bprm_mm_init fs/exec.c:393 [inline] alloc_bprm+0x8f5/0xe20 fs/exec.c:1548 kernel_execve+0x99/0xa50 fs/exec.c:1977 try_to_run_init_process init/main.c:1397 [inline] kernel_init+0xed/0x2b0 init/main.c:1525 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 -> #0 (&mm->mmap_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __might_fault+0xc6/0x120 mm/memory.c:6716 _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] ni_fiemap+0x57c/0x18c0 fs/ntfs3/frecord.c:2139 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1352 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1bf8/0x2e40 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &mm->mmap_lock --> mapping.invalidate_lock#11 --> &ni->ni_lock#3/5 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock#3/5); lock(mapping.invalidate_lock#11); lock(&ni->ni_lock#3/5); rlock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz.7.239/8027: #0: ffff8880548eef28 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1109 [inline] #0: ffff8880548eef28 (&ni->ni_lock#3/5){+.+.}-{3:3}, at: ntfs_fiemap+0xff/0x180 fs/ntfs3/file.c:1350 stack backtrace: CPU: 0 UID: 0 PID: 8027 Comm: syz.7.239 Not tainted 6.12.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120 print_circular_bug+0x13a/0x1b0 kernel/locking/lockdep.c:2074 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain+0x18ef/0x5920 kernel/locking/lockdep.c:3904 __lock_acquire+0x1384/0x2050 kernel/locking/lockdep.c:5202 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 __might_fault+0xc6/0x120 mm/memory.c:6716 _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] ni_fiemap+0x57c/0x18c0 fs/ntfs3/frecord.c:2139 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1352 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1bf8/0x2e40 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fe3f1d7e719 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:00007fe3f2b0c038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fe3f1f35f80 RCX: 00007fe3f1d7e719 RDX: 0000000020001040 RSI: 00000000c020660b RDI: 0000000000000009 RBP: 00007fe3f1df175e R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fe3f1f35f80 R15: 00007ffe6067e238 ntfs3(loop7): ino=23, "blkio.bfq.io_service_time_recursive" fallocate(0x40) is not supported