====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc2-syzkaller-g9aa9b43d689e #0 Not tainted ------------------------------------------------------ syz.0.90/7151 is trying to acquire lock: ffff0000dfbfafa8 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] ffff0000dfbfafa8 (&sb->s_type->i_mutex_key#25){+.+.}-{4:4}, at: ntfs_file_mmap+0x45c/0x5e8 fs/ntfs3/file.c:313 but task is already holding lock: ffff0000c83eaed0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] ffff0000c83eaed0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x180/0x43c mm/util.c:577 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&mm->mmap_lock){++++}-{4:4}: gup_fast_fallback+0x19c/0x2a14 mm/gup.c:3341 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3463 iov_iter_extract_user_pages lib/iov_iter.c:1846 [inline] iov_iter_extract_pages+0x294/0x514 lib/iov_iter.c:1909 dio_refill_pages fs/direct-io.c:172 [inline] dio_get_page fs/direct-io.c:213 [inline] do_direct_IO fs/direct-io.c:915 [inline] __blockdev_direct_IO+0xca8/0x2818 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3475 [inline] ntfs_direct_IO+0x1ac/0x380 fs/ntfs3/inode.c:813 generic_file_direct_write+0x1a8/0x350 mm/filemap.c:4046 __generic_file_write_iter+0x10c/0x204 mm/filemap.c:4215 ntfs_file_write_iter+0x58c/0x66c fs/ntfs3/file.c:1197 new_sync_write fs/read_write.c:593 [inline] vfs_write+0x62c/0x97c fs/read_write.c:686 ksys_write+0x120/0x210 fs/read_write.c:738 __do_sys_write fs/read_write.c:749 [inline] __se_sys_write fs/read_write.c:746 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:746 __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/0x17c arch/arm64/kernel/entry-common.c:767 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786 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:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5240 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5871 down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:867 [inline] ntfs_file_mmap+0x45c/0x5e8 fs/ntfs3/file.c:313 call_mmap include/linux/fs.h:2284 [inline] mmap_file mm/internal.h:167 [inline] __mmap_new_file_vma mm/vma.c:2405 [inline] __mmap_new_vma mm/vma.c:2467 [inline] __mmap_region mm/vma.c:2622 [inline] mmap_region+0xe9c/0x1c0c mm/vma.c:2692 do_mmap+0x968/0xfac mm/mmap.c:561 vm_mmap_pgoff+0x2b8/0x43c mm/util.c:579 ksys_mmap_pgoff+0x394/0x5b8 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+0x58/0x17c arch/arm64/kernel/entry-common.c:767 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786 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.90/7151: #0: ffff0000c83eaed0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] #0: ffff0000c83eaed0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x180/0x43c mm/util.c:577 stack backtrace: CPU: 1 UID: 0 PID: 7151 Comm: syz.0.90 Not tainted 6.16.0-rc2-syzkaller-g9aa9b43d689e #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:501 (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:2046 check_noncircular+0x154/0x174 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain kernel/locking/lockdep.c:3911 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5240 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5871 down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:867 [inline] ntfs_file_mmap+0x45c/0x5e8 fs/ntfs3/file.c:313 call_mmap include/linux/fs.h:2284 [inline] mmap_file mm/internal.h:167 [inline] __mmap_new_file_vma mm/vma.c:2405 [inline] __mmap_new_vma mm/vma.c:2467 [inline] __mmap_region mm/vma.c:2622 [inline] mmap_region+0xe9c/0x1c0c mm/vma.c:2692 do_mmap+0x968/0xfac mm/mmap.c:561 vm_mmap_pgoff+0x2b8/0x43c mm/util.c:579 ksys_mmap_pgoff+0x394/0x5b8 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+0x58/0x17c arch/arm64/kernel/entry-common.c:767 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:786 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600