======================================================
WARNING: possible circular locking dependency detected
6.1.140-syzkaller #0 Not tainted
------------------------------------------------------
syz.6.586/6874 is trying to acquire lock:
ffff8880511f1e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ffff8880511f1e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_fallocate+0x71d/0xf20 fs/ntfs3/file.c:567
but task is already holding lock:
ffff8880511f22c0 (mapping.invalidate_lock#10){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline]
ffff8880511f22c0 (mapping.invalidate_lock#10){++++}-{3:3}, at: ntfs_fallocate+0x38a/0xf20 fs/ntfs3/file.c:503
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #2 (mapping.invalidate_lock#10){++++}-{3:3}:
down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
filemap_fault+0x53c/0x1670 mm/filemap.c:3220
__do_fault+0x13b/0x4e0 mm/memory.c:4280
do_read_fault mm/memory.c:4631 [inline]
do_fault mm/memory.c:4760 [inline]
handle_pte_fault mm/memory.c:5031 [inline]
__handle_mm_fault mm/memory.c:5173 [inline]
handle_mm_fault+0x28ca/0x3e70 mm/memory.c:5294
do_user_addr_fault+0x51f/0xb10 arch/x86/mm/fault.c:1340
handle_page_fault arch/x86/mm/fault.c:1431 [inline]
exc_page_fault+0x60/0x100 arch/x86/mm/fault.c:1487
asm_exc_page_fault+0x22/0x30 arch/x86/include/asm/idtentry.h:608
copy_user_short_string+0xa/0x40 arch/x86/lib/copy_user_64.S:231
copy_user_generic arch/x86/include/asm/uaccess_64.h:37 [inline]
raw_copy_from_user arch/x86/include/asm/uaccess_64.h:52 [inline]
_copy_from_user+0xf4/0x170 lib/usercopy.c:23
copy_from_user include/linux/uaccess.h:161 [inline]
ioctl_fiemap fs/ioctl.c:209 [inline]
do_vfs_ioctl+0x5c3/0x1d10 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x83/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
-> #1 (&mm->mmap_lock){++++}-{3:3}:
__might_fault+0xc2/0x120 mm/memory.c:5852
_copy_to_user+0x27/0x130 lib/usercopy.c:36
copy_to_user include/linux/uaccess.h:169 [inline]
ni_fiemap+0x4ec/0x1300 fs/ntfs3/frecord.c:2140
ntfs_fiemap+0xd7/0x130 fs/ntfs3/file.c:1170
ioctl_fiemap fs/ioctl.c:219 [inline]
do_vfs_ioctl+0x1425/0x1d10 fs/ioctl.c:810
__do_sys_ioctl fs/ioctl.c:868 [inline]
__se_sys_ioctl+0x83/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
-> #0 (&ni->ni_lock/5){+.+.}-{3:3}:
check_prev_add kernel/locking/lockdep.c:3090 [inline]
check_prevs_add kernel/locking/lockdep.c:3209 [inline]
validate_chain kernel/locking/lockdep.c:3825 [inline]
__lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ntfs_fallocate+0x71d/0xf20 fs/ntfs3/file.c:567
vfs_fallocate+0x584/0x6f0 fs/open.c:323
ksys_fallocate fs/open.c:346 [inline]
__do_sys_fallocate fs/open.c:354 [inline]
__se_sys_fallocate fs/open.c:352 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:352
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
other info that might help us debug this:
Chain exists of:
&ni->ni_lock/5 --> &mm->mmap_lock --> mapping.invalidate_lock#10
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(mapping.invalidate_lock#10);
lock(&mm->mmap_lock);
lock(mapping.invalidate_lock#10);
lock(&ni->ni_lock/5);
*** DEADLOCK ***
3 locks held by syz.6.586/6874:
#0: ffff888063446460 (sb_writers#27){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3015 [inline]
#0: ffff888063446460 (sb_writers#27){.+.+}-{0:0}, at: vfs_fallocate+0x4f1/0x6f0 fs/open.c:322
#1: ffff8880511f2120 (&sb->s_type->i_mutex_key#33){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
#1: ffff8880511f2120 (&sb->s_type->i_mutex_key#33){+.+.}-{3:3}, at: ntfs_fallocate+0x2df/0xf20 fs/ntfs3/file.c:489
#2: ffff8880511f22c0 (mapping.invalidate_lock#10){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline]
#2: ffff8880511f22c0 (mapping.invalidate_lock#10){++++}-{3:3}, at: ntfs_fallocate+0x38a/0xf20 fs/ntfs3/file.c:503
stack backtrace:
CPU: 0 PID: 6874 Comm: syz.6.586 Not tainted 6.1.140-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
check_noncircular+0x274/0x310 kernel/locking/lockdep.c:2170
check_prev_add kernel/locking/lockdep.c:3090 [inline]
check_prevs_add kernel/locking/lockdep.c:3209 [inline]
validate_chain kernel/locking/lockdep.c:3825 [inline]
__lock_acquire+0x2cf8/0x7c50 kernel/locking/lockdep.c:5049
lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
__mutex_lock_common kernel/locking/mutex.c:603 [inline]
__mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ntfs_fallocate+0x71d/0xf20 fs/ntfs3/file.c:567
vfs_fallocate+0x584/0x6f0 fs/open.c:323
ksys_fallocate fs/open.c:346 [inline]
__do_sys_fallocate fs/open.c:354 [inline]
__se_sys_fallocate fs/open.c:352 [inline]
__x64_sys_fallocate+0xbd/0x100 fs/open.c:352
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7a3878e969
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:00007f7a3960d038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007f7a389b6080 RCX: 00007f7a3878e969
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000004
RBP: 00007f7a38810ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f7a389b6080 R15: 00007fff8fd1d5b8
</TASK>