====================================================== WARNING: possible circular locking dependency detected 6.1.138-syzkaller #0 Not tainted ------------------------------------------------------ syz.4.96/4824 is trying to acquire lock: ffff0000f4b4f240 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000f4b4f240 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 but task is already holding lock: ffff0000dffd5b48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] ffff0000dffd5b48 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x138/0x284 mm/util.c:518 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_lock){++++}-{3:3}: __might_fault+0xc4/0x124 mm/memory.c:5852 fault_in_readable+0x118/0x3e0 mm/gup.c:1908 fault_in_iov_iter_readable+0x190/0x2c4 lib/iov_iter.c:370 generic_perform_write+0x17c/0x4b0 mm/filemap.c:3836 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974 ntfs_file_write_iter+0x4d4/0x584 fs/ntfs3/file.c:1081 do_iter_readv_writev fs/read_write.c:-1 [inline] do_iter_write+0x530/0x91c fs/read_write.c:861 vfs_writev fs/read_write.c:934 [inline] do_pwritev+0x1c8/0x2fc fs/read_write.c:1031 __do_sys_pwritev2 fs/read_write.c:1090 [inline] __se_sys_pwritev2 fs/read_write.c:1081 [inline] __arm64_sys_pwritev2+0xd4/0x108 fs/read_write.c:1081 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&sb->s_type->i_mutex_key#22){+.+.}-{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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 call_mmap include/linux/fs.h:2270 [inline] mmap_file+0x6c/0xc8 mm/util.c:1109 __mmap_region mm/mmap.c:2760 [inline] mmap_region+0xcc8/0x1860 mm/mmap.c:2904 do_mmap+0x978/0x10dc mm/mmap.c:1424 vm_mmap_pgoff+0x184/0x284 mm/util.c:520 ksys_mmap_pgoff+0x3b8/0x5a0 mm/mmap.c:1470 __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:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 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#22); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#22); *** DEADLOCK *** 1 lock held by syz.4.96/4824: #0: ffff0000dffd5b48 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline] #0: ffff0000dffd5b48 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x138/0x284 mm/util.c:518 stack backtrace: CPU: 1 PID: 4824 Comm: syz.4.96 Not tainted 6.1.138-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x240/0x2d4 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+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ntfs_file_mmap+0x3e8/0x55c fs/ntfs3/file.c:320 call_mmap include/linux/fs.h:2270 [inline] mmap_file+0x6c/0xc8 mm/util.c:1109 __mmap_region mm/mmap.c:2760 [inline] mmap_region+0xcc8/0x1860 mm/mmap.c:2904 do_mmap+0x978/0x10dc mm/mmap.c:1424 vm_mmap_pgoff+0x184/0x284 mm/util.c:520 ksys_mmap_pgoff+0x3b8/0x5a0 mm/mmap.c:1470 __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:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585