====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc4-syzkaller-ge0f4c8dd9d2d #0 Not tainted ------------------------------------------------------ syz.5.306/8562 is trying to acquire lock: ffff0000dbf90a50 (&mm->mmap_lock){++++}-{4:4}, at: get_current arch/arm64/include/asm/current.h:19 [inline] ffff0000dbf90a50 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x158/0x2a14 mm/gup.c:3401 but task is already holding lock: ffff0000f8070398 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:887 [inline] ffff0000f8070398 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: ntfs_file_write_iter+0x74/0x66c fs/ntfs3/file.c:1250 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}: 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:397 call_mmap include/linux/fs.h:2243 [inline] mmap_file mm/internal.h:167 [inline] __mmap_new_file_vma mm/vma.c:2353 [inline] __mmap_new_vma mm/vma.c:2417 [inline] __mmap_region mm/vma.c:2519 [inline] mmap_region+0xc34/0x1a24 mm/vma.c:2597 do_mmap+0x968/0xf78 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/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&mm->mmap_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1728/0x3058 kernel/locking/lockdep.c:5235 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5866 gup_fast_fallback+0x19c/0x2a14 mm/gup.c:3401 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3523 iov_iter_extract_user_pages lib/iov_iter.c:1849 [inline] iov_iter_extract_pages+0x294/0x514 lib/iov_iter.c:1912 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:3422 [inline] ntfs_direct_IO+0x170/0x320 fs/ntfs3/inode.c:809 generic_file_direct_write+0x1a8/0x350 mm/filemap.c:4037 __generic_file_write_iter+0x10c/0x204 mm/filemap.c:4206 ntfs_file_write_iter+0x58c/0x66c fs/ntfs3/file.c:1287 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x62c/0x97c fs/read_write.c:684 ksys_pwrite64 fs/read_write.c:791 [inline] __do_sys_pwrite64 fs/read_write.c:799 [inline] __se_sys_pwrite64 fs/read_write.c:796 [inline] __arm64_sys_pwrite64+0x170/0x208 fs/read_write.c:796 __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/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/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(&sb->s_type->i_mutex_key#30); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#30); rlock(&mm->mmap_lock); *** DEADLOCK *** 2 locks held by syz.5.306/8562: #0: ffff0000cd770420 (sb_writers#12){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3041 [inline] #0: ffff0000cd770420 (sb_writers#12){.+.+}-{0:0}, at: vfs_write+0x244/0x97c fs/read_write.c:680 #1: ffff0000f8070398 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:887 [inline] #1: ffff0000f8070398 (&sb->s_type->i_mutex_key#30){+.+.}-{4:4}, at: ntfs_file_write_iter+0x74/0x66c fs/ntfs3/file.c:1250 stack backtrace: CPU: 0 UID: 0 PID: 8562 Comm: syz.5.306 Not tainted 6.15.0-rc4-syzkaller-ge0f4c8dd9d2d #0 PREEMPT 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+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:2079 check_noncircular+0x154/0x174 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1728/0x3058 kernel/locking/lockdep.c:5235 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5866 gup_fast_fallback+0x19c/0x2a14 mm/gup.c:3401 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3523 iov_iter_extract_user_pages lib/iov_iter.c:1849 [inline] iov_iter_extract_pages+0x294/0x514 lib/iov_iter.c:1912 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:3422 [inline] ntfs_direct_IO+0x170/0x320 fs/ntfs3/inode.c:809 generic_file_direct_write+0x1a8/0x350 mm/filemap.c:4037 __generic_file_write_iter+0x10c/0x204 mm/filemap.c:4206 ntfs_file_write_iter+0x58c/0x66c fs/ntfs3/file.c:1287 new_sync_write fs/read_write.c:591 [inline] vfs_write+0x62c/0x97c fs/read_write.c:684 ksys_pwrite64 fs/read_write.c:791 [inline] __do_sys_pwrite64 fs/read_write.c:799 [inline] __se_sys_pwrite64 fs/read_write.c:796 [inline] __arm64_sys_pwrite64+0x170/0x208 fs/read_write.c:796 __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/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600