====================================================== WARNING: possible circular locking dependency detected 6.9.0-rc3-syzkaller-gb5d2afe8745b #0 Not tainted ------------------------------------------------------ syz-executor.4/9499 is trying to acquire lock: ffff0000df61e0e0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1121 [inline] ffff0000df61e0e0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_fallocate+0x754/0xe94 fs/ntfs3/file.c:572 but task is already holding lock: ffff0000df61e520 (mapping.invalidate_lock#9){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:840 [inline] ffff0000df61e520 (mapping.invalidate_lock#9){++++}-{3:3}, at: ntfs_fallocate+0x350/0xe94 fs/ntfs3/file.c:486 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #3 (mapping.invalidate_lock#9){++++}-{3:3}: down_read+0x58/0x2fc kernel/locking/rwsem.c:1526 filemap_invalidate_lock_shared include/linux/fs.h:850 [inline] filemap_fault+0x4f8/0x1004 mm/filemap.c:3277 __do_fault+0x11c/0x374 mm/memory.c:4531 do_read_fault mm/memory.c:4894 [inline] do_fault mm/memory.c:5024 [inline] do_pte_missing mm/memory.c:3880 [inline] handle_pte_fault mm/memory.c:5300 [inline] __handle_mm_fault+0x36d0/0x5920 mm/memory.c:5441 handle_mm_fault+0x1e8/0x63c mm/memory.c:5606 faultin_page mm/gup.c:958 [inline] __get_user_pages+0x3e0/0xa24 mm/gup.c:1241 faultin_vma_page_range+0x1dc/0x278 mm/gup.c:1739 madvise_populate mm/madvise.c:930 [inline] madvise_vma_behavior mm/madvise.c:1039 [inline] madvise_walk_vmas mm/madvise.c:1261 [inline] do_madvise+0x15a8/0x303c mm/madvise.c:1441 __do_sys_madvise mm/madvise.c:1454 [inline] __se_sys_madvise mm/madvise.c:1452 [inline] __arm64_sys_madvise+0xa4/0xc0 mm/madvise.c:1452 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #2 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc4/0x124 mm/memory.c:6220 _copy_to_user include/linux/uaccess.h:165 [inline] copy_to_user include/linux/uaccess.h:191 [inline] fiemap_fill_next_extent+0x1b4/0x424 fs/ioctl.c:145 ni_fiemap+0x7dc/0xe10 fs/ntfs3/frecord.c:2065 ntfs_fiemap+0x110/0x168 fs/ntfs3/file.c:1206 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c18/0x2ab0 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl fs/ioctl.c:890 [inline] __arm64_sys_ioctl+0xe4/0x1c8 fs/ioctl.c:890 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #1 (&ni->file.run_lock#3){++++}-{3:3}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1579 ntfs_set_size+0x130/0x200 fs/ntfs3/inode.c:837 ntfs_extend+0x130/0x3dc fs/ntfs3/file.c:335 ntfs_file_write_iter+0x338/0x628 fs/ntfs3/file.c:1115 call_write_iter include/linux/fs.h:2110 [inline] new_sync_write fs/read_write.c:497 [inline] vfs_write+0x968/0xc3c fs/read_write.c:590 ksys_write+0x15c/0x26c fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:652 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 -> #0 (&ni->ni_lock/4){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x248/0x73c kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1121 [inline] ntfs_fallocate+0x754/0xe94 fs/ntfs3/file.c:572 vfs_fallocate+0x480/0x5bc fs/open.c:330 ksys_fallocate fs/open.c:353 [inline] __do_sys_fallocate fs/open.c:361 [inline] __se_sys_fallocate fs/open.c:359 [inline] __arm64_sys_fallocate+0xc0/0x110 fs/open.c:359 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 other info that might help us debug this: Chain exists of: &ni->ni_lock/4 --> &mm->mmap_lock --> mapping.invalidate_lock#9 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#9); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#9); lock(&ni->ni_lock/4); *** DEADLOCK *** 3 locks held by syz-executor.4/9499: #0: ffff0000ee48c420 (sb_writers#15){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2855 [inline] #0: ffff0000ee48c420 (sb_writers#15){.+.+}-{0:0}, at: vfs_fallocate+0x40c/0x5bc fs/open.c:329 #1: ffff0000df61e380 (&sb->s_type->i_mutex_key#34){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:795 [inline] #1: ffff0000df61e380 (&sb->s_type->i_mutex_key#34){+.+.}-{3:3}, at: ntfs_fallocate+0x2a0/0xe94 fs/ntfs3/file.c:472 #2: ffff0000df61e520 (mapping.invalidate_lock#9){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:840 [inline] #2: ffff0000df61e520 (mapping.invalidate_lock#9){++++}-{3:3}, at: ntfs_fallocate+0x350/0xe94 fs/ntfs3/file.c:486 stack backtrace: CPU: 0 PID: 9499 Comm: syz-executor.4 Not tainted 6.9.0-rc3-syzkaller-gb5d2afe8745b #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:317 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:324 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:114 dump_stack+0x1c/0x28 lib/dump_stack.c:123 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2060 check_noncircular+0x310/0x404 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 kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x248/0x73c kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:608 __mutex_lock kernel/locking/mutex.c:752 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:804 ni_lock fs/ntfs3/ntfs_fs.h:1121 [inline] ntfs_fallocate+0x754/0xe94 fs/ntfs3/file.c:572 vfs_fallocate+0x480/0x5bc fs/open.c:330 ksys_fallocate fs/open.c:353 [inline] __do_sys_fallocate fs/open.c:361 [inline] __se_sys_fallocate fs/open.c:359 [inline] __arm64_sys_fallocate+0xc0/0x110 fs/open.c:359 __invoke_syscall arch/arm64/kernel/syscall.c:34 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:48 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:133 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:152 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598