syzbot

======================================================
WARNING: possible circular locking dependency detected
6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 Not tainted
------------------------------------------------------
syz.3.855/8482 is trying to acquire lock:
ffff0000f5573468 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
ffff0000f5573468 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ntfs_fallocate+0x450/0xdd4 fs/ntfs3/file.c:561

but task is already holding lock:
ffff0000f55738a0 (mapping.invalidate_lock#3){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:924 [inline]
ffff0000f55738a0 (mapping.invalidate_lock#3){++++}-{4:4}, at: ntfs_fallocate+0x324/0xdd4 fs/ntfs3/file.c:546

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (mapping.invalidate_lock#3){++++}-{4:4}:
       down_read+0x58/0x2f8 kernel/locking/rwsem.c:1537
       filemap_invalidate_lock_shared include/linux/fs.h:934 [inline]
       filemap_fault+0x3fc/0x1280 mm/filemap.c:3433
       __do_fault+0x1fc/0x4cc mm/memory.c:5152
       do_read_fault mm/memory.c:5573 [inline]
       do_fault mm/memory.c:5707 [inline]
       do_pte_missing mm/memory.c:4234 [inline]
       handle_pte_fault mm/memory.c:6052 [inline]
       __handle_mm_fault mm/memory.c:6195 [inline]
       handle_mm_fault+0x2c90/0x4d34 mm/memory.c:6364
       do_page_fault+0x57c/0x13cc arch/arm64/mm/fault.c:696
       do_translation_fault+0xc4/0x114 arch/arm64/mm/fault.c:789
       do_mem_abort+0x70/0x194 arch/arm64/mm/fault.c:929
       el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:481
       el1h_64_sync_handler+0x50/0xfc arch/arm64/kernel/entry-common.c:597
       el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:591
       __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:-1 [inline]
       do_strncpy_from_user lib/strncpy_from_user.c:41 [inline]
       strncpy_from_user+0x198/0x370 lib/strncpy_from_user.c:149
       getname_flags+0xe8/0x470 fs/namei.c:157
       getname include/linux/fs.h:2918 [inline]
       __do_sys_symlinkat fs/namei.c:4772 [inline]
       __se_sys_symlinkat fs/namei.c:4769 [inline]
       __arm64_sys_symlinkat+0x7c/0xb4 fs/namei.c:4769
       __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
       el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
       do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
       el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879
       el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898
       el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

-> #1 (&mm->mmap_lock){++++}-{4:4}:
       __might_fault+0xc4/0x124 mm/memory.c:6958
       _inline_copy_to_user include/linux/uaccess.h:192 [inline]
       copy_to_user include/linux/uaccess.h:223 [inline]
       fiemap_fill_next_extent+0x17c/0x3f0 fs/ioctl.c:145
       ni_fiemap+0x2e8/0x9ec fs/ntfs3/frecord.c:1896
       ntfs_fiemap+0x10c/0x188 fs/ntfs3/file.c:1326
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x1140/0x1834 fs/ioctl.c:532
       __do_sys_ioctl fs/ioctl.c:596 [inline]
       __se_sys_ioctl fs/ioctl.c:584 [inline]
       __arm64_sys_ioctl+0xe4/0x1c4 fs/ioctl.c:584
       __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
       el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
       do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
       el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879
       el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898
       el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

-> #0 (&ni->ni_lock#3/5){+.+.}-{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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
       lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
       __mutex_lock_common+0x1d0/0x24ac kernel/locking/mutex.c:598
       __mutex_lock kernel/locking/mutex.c:760 [inline]
       mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812
       ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
       ntfs_fallocate+0x450/0xdd4 fs/ntfs3/file.c:561
       vfs_fallocate+0x52c/0x668 fs/open.c:342
       ioctl_preallocate fs/ioctl.c:290 [inline]
       file_ioctl+0x584/0x75c fs/ioctl.c:-1
       do_vfs_ioctl+0xa10/0x1834 fs/ioctl.c:577
       __do_sys_ioctl fs/ioctl.c:596 [inline]
       __se_sys_ioctl fs/ioctl.c:584 [inline]
       __arm64_sys_ioctl+0xe4/0x1c4 fs/ioctl.c:584
       __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
       invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
       el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
       do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
       el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879
       el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898
       el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

other info that might help us debug this:

Chain exists of:
  &ni->ni_lock#3/5 --> &mm->mmap_lock --> mapping.invalidate_lock#3

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(mapping.invalidate_lock#3);
                               lock(&mm->mmap_lock);
                               lock(mapping.invalidate_lock#3);
  lock(&ni->ni_lock#3/5);

 *** DEADLOCK ***

3 locks held by syz.3.855/8482:
 #0: ffff0000dd148428 (sb_writers#11){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3107 [inline]
 #0: ffff0000dd148428 (sb_writers#11){.+.+}-{0:0}, at: vfs_fallocate+0x4d0/0x668 fs/open.c:341
 #1: ffff0000f5573700 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
 #1: ffff0000f5573700 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: ntfs_fallocate+0x270/0xdd4 fs/ntfs3/file.c:532
 #2: ffff0000f55738a0 (mapping.invalidate_lock#3){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:924 [inline]
 #2: ffff0000f55738a0 (mapping.invalidate_lock#3){++++}-{4:4}, at: ntfs_fallocate+0x324/0xdd4 fs/ntfs3/file.c:546

stack backtrace:
CPU: 1 UID: 0 PID: 8482 Comm: syz.3.855 Not tainted 6.17.0-rc1-syzkaller-g8f5ae30d69d7 #0 PREEMPT 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/30/2025
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 dump_stack+0x1c/0x28 lib/dump_stack.c:129
 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043
 check_noncircular+0x154/0x174 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+0x1774/0x30a4 kernel/locking/lockdep.c:5237
 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868
 __mutex_lock_common+0x1d0/0x24ac kernel/locking/mutex.c:598
 __mutex_lock kernel/locking/mutex.c:760 [inline]
 mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:812
 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
 ntfs_fallocate+0x450/0xdd4 fs/ntfs3/file.c:561
 vfs_fallocate+0x52c/0x668 fs/open.c:342
 ioctl_preallocate fs/ioctl.c:290 [inline]
 file_ioctl+0x584/0x75c fs/ioctl.c:-1
 do_vfs_ioctl+0xa10/0x1834 fs/ioctl.c:577
 __do_sys_ioctl fs/ioctl.c:596 [inline]
 __se_sys_ioctl fs/ioctl.c:584 [inline]
 __arm64_sys_ioctl+0xe4/0x1c4 fs/ioctl.c:584
 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49
 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132
 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151
 el0_svc+0x58/0x180 arch/arm64/kernel/entry-common.c:879
 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:898
 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596