======================================================
WARNING: possible circular locking dependency detected
6.14.0-rc7-syzkaller-ga2392f333575 #0 Not tainted
------------------------------------------------------
syz.0.143/7296 is trying to acquire lock:
ffff0000dd3b9248 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:877 [inline]
ffff0000dd3b9248 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: ntfs_file_mmap+0x48c/0x6b8 fs/ntfs3/file.c:379
but task is already holding lock:
ffff0000cbbebd50 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:152 [inline]
ffff0000cbbebd50 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1c0/0x4ac mm/util.c:576
which lock already depends on the new lock.
the existing dependency chain (in reverse order) is:
-> #1 (&mm->mmap_lock){++++}-{4:4}:
down_read_killable+0x64/0x338 kernel/locking/rwsem.c:1547
mmap_read_lock_killable+0x28/0x360 include/linux/mmap_lock.h:199
get_mmap_lock_carefully mm/memory.c:6246 [inline]
lock_mm_and_find_vma+0x2a4/0x2d8 mm/memory.c:6297
do_page_fault+0x4e0/0x10ac arch/arm64/mm/fault.c:668
do_translation_fault+0xc4/0x114 arch/arm64/mm/fault.c:783
do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:919
el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:432
el1h_64_sync_handler+0x60/0xcc arch/arm64/kernel/entry-common.c:510
el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:595
__uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:169 [inline]
fault_in_readable+0x168/0x310 mm/gup.c:2234
fault_in_iov_iter_readable+0x1dc/0x22c lib/iov_iter.c:94
generic_perform_write+0x1f8/0x868 mm/filemap.c:4092
__generic_file_write_iter+0xfc/0x204 mm/filemap.c:4203
ntfs_file_write_iter+0x590/0x674 fs/ntfs3/file.c:1267
do_iter_readv_writev+0x558/0x7d8
vfs_writev+0x2dc/0x92c fs/read_write.c:1050
do_pwritev fs/read_write.c:1146 [inline]
__do_sys_pwritev2 fs/read_write.c:1204 [inline]
__se_sys_pwritev2 fs/read_write.c:1195 [inline]
__arm64_sys_pwritev2+0x1d8/0x2ec fs/read_write.c:1195
__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+0x54/0x168 arch/arm64/kernel/entry-common.c:744
el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
-> #0 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}:
check_prev_add kernel/locking/lockdep.c:3163 [inline]
check_prevs_add kernel/locking/lockdep.c:3282 [inline]
validate_chain kernel/locking/lockdep.c:3906 [inline]
__lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5228
lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
down_write+0x50/0xc0 kernel/locking/rwsem.c:1577
inode_lock include/linux/fs.h:877 [inline]
ntfs_file_mmap+0x48c/0x6b8 fs/ntfs3/file.c:379
call_mmap include/linux/fs.h:2245 [inline]
mmap_file mm/internal.h:124 [inline]
__mmap_new_file_vma mm/vma.c:2296 [inline]
__mmap_new_vma mm/vma.c:2360 [inline]
__mmap_region mm/vma.c:2461 [inline]
mmap_region+0x1ae0/0x2518 mm/vma.c:2539
do_mmap+0xbc8/0x1150 mm/mmap.c:561
vm_mmap_pgoff+0x30c/0x4ac mm/util.c:578
ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:607
__do_sys_mmap arch/arm64/kernel/sys.c:28 [inline]
__se_sys_mmap arch/arm64/kernel/sys.c:21 [inline]
__arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21
__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+0x54/0x168 arch/arm64/kernel/entry-common.c:744
el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&mm->mmap_lock);
lock(&sb->s_type->i_mutex_key#25);
lock(&mm->mmap_lock);
lock(&sb->s_type->i_mutex_key#25);
*** DEADLOCK ***
1 lock held by syz.0.143/7296:
#0: ffff0000cbbebd50 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:152 [inline]
#0: ffff0000cbbebd50 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1c0/0x4ac mm/util.c:576
stack backtrace:
CPU: 0 UID: 0 PID: 7296 Comm: syz.0.143 Not tainted 6.14.0-rc7-syzkaller-ga2392f333575 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C)
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120
dump_stack+0x1c/0x28 lib/dump_stack.c:129
print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2076
check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2208
check_prev_add kernel/locking/lockdep.c:3163 [inline]
check_prevs_add kernel/locking/lockdep.c:3282 [inline]
validate_chain kernel/locking/lockdep.c:3906 [inline]
__lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5228
lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5851
down_write+0x50/0xc0 kernel/locking/rwsem.c:1577
inode_lock include/linux/fs.h:877 [inline]
ntfs_file_mmap+0x48c/0x6b8 fs/ntfs3/file.c:379
call_mmap include/linux/fs.h:2245 [inline]
mmap_file mm/internal.h:124 [inline]
__mmap_new_file_vma mm/vma.c:2296 [inline]
__mmap_new_vma mm/vma.c:2360 [inline]
__mmap_region mm/vma.c:2461 [inline]
mmap_region+0x1ae0/0x2518 mm/vma.c:2539
do_mmap+0xbc8/0x1150 mm/mmap.c:561
vm_mmap_pgoff+0x30c/0x4ac mm/util.c:578
ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:607
__do_sys_mmap arch/arm64/kernel/sys.c:28 [inline]
__se_sys_mmap arch/arm64/kernel/sys.c:21 [inline]
__arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21
__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+0x54/0x168 arch/arm64/kernel/entry-common.c:744
el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762
el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600