====================================================== WARNING: possible circular locking dependency detected 6.10.0-syzkaller-05505-gb1bc554e009e #0 Not tainted ------------------------------------------------------ syz.3.100/5927 is trying to acquire lock: ffff88802d34ba98 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xaa/0x120 mm/memory.c:6234 but task is already holding lock: ffff8880776f59d0 (&ni->file.run_lock#3){++++}-{3:3}, at: ni_fiemap+0x373/0x1230 fs/ntfs3/frecord.c:1961 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&ni->file.run_lock#3){++++}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5753 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526 attr_data_get_block+0x2e3/0x2e10 fs/ntfs3/attrib.c:902 ntfs_get_block_vbo+0x3e4/0xd50 fs/ntfs3/inode.c:599 do_mpage_readpage+0x827/0x1c80 fs/mpage.c:225 mpage_read_folio+0x108/0x1e0 fs/mpage.c:392 filemap_read_folio+0x1a0/0x790 mm/filemap.c:2355 filemap_fault+0xf69/0x1760 mm/filemap.c:3406 __do_fault+0x135/0x460 mm/memory.c:4556 do_shared_fault mm/memory.c:4981 [inline] do_fault mm/memory.c:5055 [inline] do_pte_missing mm/memory.c:3897 [inline] handle_pte_fault+0x119b/0x7090 mm/memory.c:5381 __handle_mm_fault mm/memory.c:5524 [inline] handle_mm_fault+0xfb0/0x19d0 mm/memory.c:5689 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 -> #2 (mapping.invalidate_lock#5){.+.+}-{3:3}: lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5753 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526 filemap_invalidate_lock_shared include/linux/fs.h:854 [inline] filemap_fault+0x658/0x1760 mm/filemap.c:3302 __do_fault+0x135/0x460 mm/memory.c:4556 do_shared_fault mm/memory.c:4981 [inline] do_fault mm/memory.c:5055 [inline] do_pte_missing mm/memory.c:3897 [inline] handle_pte_fault+0x119b/0x7090 mm/memory.c:5381 __handle_mm_fault mm/memory.c:5524 [inline] handle_mm_fault+0xfb0/0x19d0 mm/memory.c:5689 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:5753 down_write+0x99/0x220 kernel/locking/rwsem.c:1579 vma_start_write include/linux/mm.h:736 [inline] vma_link+0x270/0x4f0 mm/mmap.c:416 insert_vm_struct+0x2f7/0x410 mm/mmap.c:3413 __bprm_mm_init fs/exec.c:291 [inline] bprm_mm_init fs/exec.c:395 [inline] alloc_bprm+0x81f/0xda0 fs/exec.c:1623 kernel_execve+0x99/0xa50 fs/exec.c:2046 try_to_run_init_process init/main.c:1395 [inline] kernel_init+0xed/0x2b0 init/main.c:1523 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:3133 [inline] check_prevs_add kernel/locking/lockdep.c:3252 [inline] validate_chain+0x18e0/0x5900 kernel/locking/lockdep.c:3868 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5136 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5753 __might_fault+0xc6/0x120 mm/memory.c:6234 _copy_to_user+0x2a/0xb0 lib/usercopy.c:41 copy_to_user include/linux/uaccess.h:191 [inline] fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145 ni_fiemap+0x9b2/0x1230 fs/ntfs3/frecord.c:2044 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1215 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 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#5 --> &ni->file.run_lock#3 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(&ni->file.run_lock#3); lock(mapping.invalidate_lock#5); lock(&ni->file.run_lock#3); rlock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz.3.100/5927: #0: ffff8880776f5920 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1123 [inline] #0: ffff8880776f5920 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_fiemap+0xff/0x180 fs/ntfs3/file.c:1213 #1: ffff8880776f59d0 (&ni->file.run_lock#3){++++}-{3:3}, at: ni_fiemap+0x373/0x1230 fs/ntfs3/frecord.c:1961 stack backtrace: CPU: 1 PID: 5927 Comm: syz.3.100 Not tainted 6.10.0-syzkaller-05505-gb1bc554e009e #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 check_noncircular+0x36a/0x4a0 kernel/locking/lockdep.c:2186 check_prev_add kernel/locking/lockdep.c:3133 [inline] check_prevs_add kernel/locking/lockdep.c:3252 [inline] validate_chain+0x18e0/0x5900 kernel/locking/lockdep.c:3868 __lock_acquire+0x1346/0x1fd0 kernel/locking/lockdep.c:5136 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5753 __might_fault+0xc6/0x120 mm/memory.c:6234 _copy_to_user+0x2a/0xb0 lib/usercopy.c:41 copy_to_user include/linux/uaccess.h:191 [inline] fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145 ni_fiemap+0x9b2/0x1230 fs/ntfs3/frecord.c:2044 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1215 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 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:0x7f375cf75b59 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:00007f375dcb0048 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f375d103f60 RCX: 00007f375cf75b59 RDX: 0000000020000280 RSI: 00000000c020660b RDI: 0000000000000006 RBP: 00007f375cfe4e5d R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f375d103f60 R15: 00007ffe292f89f8