====================================================== WARNING: possible circular locking dependency detected 6.7.0-rc8-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor220/5058 is trying to acquire lock: ffff888079f273e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:857 [inline] ffff888079f273e0 (mapping.invalidate_lock#3){.+.+}-{3:3}, at: filemap_fault+0x646/0x1670 mm/filemap.c:3234 but task is already holding lock: ffff8880275f9658 (&vma->vm_lock->lock){++++}-{3:3}, at: vma_start_read include/linux/mm.h:663 [inline] ffff8880275f9658 (&vma->vm_lock->lock){++++}-{3:3}, at: lock_vma_under_rcu+0x2f6/0x6f0 mm/memory.c:5501 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (&vma->vm_lock->lock){++++}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 down_write+0x3a/0x50 kernel/locking/rwsem.c:1579 vma_start_write include/linux/mm.h:716 [inline] vma_link+0x2c9/0x540 mm/mmap.c:404 insert_vm_struct+0x19f/0x260 mm/mmap.c:3378 __bprm_mm_init fs/exec.c:281 [inline] bprm_mm_init fs/exec.c:383 [inline] alloc_bprm+0x4d5/0x900 fs/exec.c:1532 kernel_execve+0x96/0xa20 fs/exec.c:1987 call_usermodehelper_exec_async+0x233/0x370 kernel/umh.c:110 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242 -> #2 (&mm->mmap_lock){++++}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 __might_fault+0xc1/0x120 mm/memory.c:5956 _copy_to_user+0x2a/0xa0 lib/usercopy.c:36 copy_to_user include/linux/uaccess.h:191 [inline] fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145 ni_fiemap+0xa5e/0x1230 fs/ntfs3/frecord.c:2065 ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1164 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x19ea/0x2b40 fs/ioctl.c:811 __do_sys_ioctl fs/ioctl.c:869 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x45/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b -> #1 (&ni->file.run_lock#3){++++}-{3:3}: lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526 attr_data_get_block+0x2e7/0x2da0 fs/ntfs3/attrib.c:902 ntfs_get_block_vbo+0x36a/0xd00 fs/ntfs3/inode.c:589 do_mpage_readpage+0x90c/0x1f60 fs/mpage.c:233 mpage_read_folio+0x108/0x1d0 fs/mpage.c:399 filemap_read_folio+0x19c/0x780 mm/filemap.c:2323 filemap_fault+0xea8/0x1670 mm/filemap.c:3334 __do_fault+0x133/0x4e0 mm/memory.c:4266 do_shared_fault mm/memory.c:4693 [inline] do_fault mm/memory.c:4767 [inline] do_pte_missing mm/memory.c:3731 [inline] handle_pte_fault mm/memory.c:5039 [inline] __handle_mm_fault mm/memory.c:5180 [inline] handle_mm_fault+0x21e9/0x6680 mm/memory.c:5345 do_user_addr_fault arch/x86/mm/fault.c:1364 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 -> #0 (mapping.invalidate_lock#3){.+.+}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526 filemap_invalidate_lock_shared include/linux/fs.h:857 [inline] filemap_fault+0x646/0x1670 mm/filemap.c:3234 __do_fault+0x133/0x4e0 mm/memory.c:4266 do_shared_fault mm/memory.c:4693 [inline] do_fault mm/memory.c:4767 [inline] do_pte_missing mm/memory.c:3731 [inline] handle_pte_fault mm/memory.c:5039 [inline] __handle_mm_fault mm/memory.c:5180 [inline] handle_mm_fault+0x21e9/0x6680 mm/memory.c:5345 do_user_addr_fault arch/x86/mm/fault.c:1364 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 other info that might help us debug this: Chain exists of: mapping.invalidate_lock#3 --> &mm->mmap_lock --> &vma->vm_lock->lock Possible unsafe locking scenario: CPU0 CPU1 ---- ---- rlock(&vma->vm_lock->lock); lock(&mm->mmap_lock); lock(&vma->vm_lock->lock); rlock(mapping.invalidate_lock#3); *** DEADLOCK *** 1 lock held by syz-executor220/5058: #0: ffff8880275f9658 (&vma->vm_lock->lock){++++}-{3:3}, at: vma_start_read include/linux/mm.h:663 [inline] #0: ffff8880275f9658 (&vma->vm_lock->lock){++++}-{3:3}, at: lock_vma_under_rcu+0x2f6/0x6f0 mm/memory.c:5501 stack backtrace: CPU: 1 PID: 5058 Comm: syz-executor220 Not tainted 6.7.0-rc8-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x366/0x490 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain+0x1909/0x5ab0 kernel/locking/lockdep.c:3869 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754 down_read+0xb1/0xa40 kernel/locking/rwsem.c:1526 filemap_invalidate_lock_shared include/linux/fs.h:857 [inline] filemap_fault+0x646/0x1670 mm/filemap.c:3234 __do_fault+0x133/0x4e0 mm/memory.c:4266 do_shared_fault mm/memory.c:4693 [inline] do_fault mm/memory.c:4767 [inline] do_pte_missing mm/memory.c:3731 [inline] handle_pte_fault mm/memory.c:5039 [inline] __handle_mm_fault mm/memory.c:5180 [inline] handle_mm_fault+0x21e9/0x6680 mm/memory.c:5345 do_user_addr_fault arch/x86/mm/fault.c:1364 [inline] handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 RIP: 0033:0x7f704f02989f Code: a7 c5 09 00 0f 11 04 25 89 00 00 20 48 8b 35 78 a8 0c 00 e8 53 42 03 00 b8 33 00 00 00 48 89 ee 31 d2 66 0f 6f 05 21 c5 09 00 <66> 89 04 25 44 f7 01 20 bf 10 10 00 20 48 b8 2e 2f 66 69 6c 65 32 RSP: 002b:00007fff6a612e00 EFLAGS: 00010246 RAX: 0000000000000033 RBX: 00007f704f0a6066 RCX: 00007f704f05daf9 RDX: 0000000000000000 RSI: 00007f704f0a604b RDI: 0000000000000004 RBP: 00007f704f0a604b R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007f704f0a6510 R13: 00007f704f0a6055 R14: 23f2bfc581b02e40 R15: ad9a13bd00000000