====================================================== WARNING: possible circular locking dependency detected 6.14.0-rc7-syzkaller-gcc8f508710d1 #0 Not tainted ------------------------------------------------------ syz.5.328/8171 is trying to acquire lock: ffff0000dc0912d0 (&mm->mmap_lock){++++}-{4:4}, at: get_current arch/arm64/include/asm/current.h:19 [inline] ffff0000dc0912d0 (&mm->mmap_lock){++++}-{4:4}, at: gup_fast_fallback+0x1a0/0x3080 mm/gup.c:3406 but task is already holding lock: ffff0000f1482fa8 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:897 [inline] ffff0000f1482fa8 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: ntfs_file_write_iter+0x210/0x674 fs/ntfs3/file.c:1240 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}: 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 -> #0 (&mm->mmap_lock){++++}-{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 gup_fast_fallback+0x1e4/0x3080 mm/gup.c:3406 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3530 iov_iter_extract_user_pages lib/iov_iter.c:1845 [inline] iov_iter_extract_pages+0x348/0x678 lib/iov_iter.c:1908 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+0xdf0/0x3648 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3412 [inline] ntfs_direct_IO+0x170/0x300 fs/ntfs3/inode.c:809 generic_file_direct_write+0x1a8/0x350 mm/filemap.c:4025 __generic_file_write_iter+0x110/0x204 mm/filemap.c:4189 ntfs_file_write_iter+0x590/0x674 fs/ntfs3/file.c:1267 aio_write+0x36c/0x4f8 fs/aio.c:1633 io_submit_one+0x79c/0x14e0 fs/aio.c:2052 __do_sys_io_submit fs/aio.c:2111 [inline] __se_sys_io_submit fs/aio.c:2081 [inline] __arm64_sys_io_submit+0x208/0x38c fs/aio.c:2081 __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(&sb->s_type->i_mutex_key#34); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#34); rlock(&mm->mmap_lock); *** DEADLOCK *** 1 lock held by syz.5.328/8171: #0: ffff0000f1482fa8 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:897 [inline] #0: ffff0000f1482fa8 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: ntfs_file_write_iter+0x210/0x674 fs/ntfs3/file.c:1240 stack backtrace: CPU: 0 UID: 0 PID: 8171 Comm: syz.5.328 Not tainted 6.14.0-rc7-syzkaller-gcc8f508710d1 #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 gup_fast_fallback+0x1e4/0x3080 mm/gup.c:3406 pin_user_pages_fast+0xa4/0x100 mm/gup.c:3530 iov_iter_extract_user_pages lib/iov_iter.c:1845 [inline] iov_iter_extract_pages+0x348/0x678 lib/iov_iter.c:1908 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+0xdf0/0x3648 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3412 [inline] ntfs_direct_IO+0x170/0x300 fs/ntfs3/inode.c:809 generic_file_direct_write+0x1a8/0x350 mm/filemap.c:4025 __generic_file_write_iter+0x110/0x204 mm/filemap.c:4189 ntfs_file_write_iter+0x590/0x674 fs/ntfs3/file.c:1267 aio_write+0x36c/0x4f8 fs/aio.c:1633 io_submit_one+0x79c/0x14e0 fs/aio.c:2052 __do_sys_io_submit fs/aio.c:2111 [inline] __se_sys_io_submit fs/aio.c:2081 [inline] __arm64_sys_io_submit+0x208/0x38c fs/aio.c:2081 __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