====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc2-syzkaller-00130-g150b567e0d57 #0 Not tainted ------------------------------------------------------ syz.0.973/11328 is trying to acquire lock: ffff888054c66a68 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:818 [inline] ffff888054c66a68 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4}, at: ntfs_file_mmap+0x610/0x780 fs/ntfs3/file.c:379 but task is already holding lock: ffff88802fc632a0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x160/0x360 mm/util.c:578 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+0x11f8/0x2690 mm/gup.c:3416 pin_user_pages_fast+0xa8/0x100 mm/gup.c:3540 iov_iter_extract_user_pages lib/iov_iter.c:1844 [inline] iov_iter_extract_pages+0x3a5/0x2010 lib/iov_iter.c:1907 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+0x2ec5/0x40b0 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3313 [inline] ntfs_direct_IO+0x26f/0x460 fs/ntfs3/inode.c:806 generic_file_direct_write+0x19a/0x410 mm/filemap.c:3978 __generic_file_write_iter+0x11b/0x240 mm/filemap.c:4142 ntfs_file_write_iter+0xe4e/0x2300 fs/ntfs3/file.c:1267 do_iter_readv_writev+0x535/0x7f0 fs/read_write.c:820 vfs_writev+0x363/0xdd0 fs/read_write.c:1050 do_pwritev+0x1b1/0x270 fs/read_write.c:1146 __do_sys_pwritev2 fs/read_write.c:1204 [inline] __se_sys_pwritev2 fs/read_write.c:1195 [inline] __x64_sys_pwritev2+0xef/0x160 fs/read_write.c:1195 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sb->s_type->i_mutex_key#22){+.+.}-{4:4} : check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ntfs_file_mmap+0x610/0x780 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2183 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2291 [inline] __mmap_new_vma mm/vma.c:2355 [inline] __mmap_region+0x1789/0x2670 mm/vma.c:2456 mmap_region+0x270/0x320 mm/mmap.c:1348 do_mmap+0xc00/0xfc0 mm/mmap.c:496 vm_mmap_pgoff+0x1ba/0x360 mm/util.c:580 ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:542 __do_sys_mmap arch/x86/kernel/sys_x86_64.c:89 [inline] __se_sys_mmap arch/x86/kernel/sys_x86_64.c:82 [inline] __x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:82 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f 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.0.973/11328: #0: ffff88802fc632a0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:122 [inline] #0: ffff88802fc632a0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x160/0x360 mm/util.c:578 stack backtrace: CPU: 1 UID: 0 PID: 11328 Comm: syz.0.973 Not tainted 6.13.0-rc2-syzkaller-00130-g150b567e0d57 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/25/2024 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x419/0x5d0 kernel/locking/lockdep.c:2074 check_noncircular+0x31a/0x400 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x249e/0x3c40 kernel/locking/lockdep.c:5226 lock_acquire.part.0+0x11b/0x380 kernel/locking/lockdep.c:5849 down_write+0x93/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ntfs_file_mmap+0x610/0x780 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2183 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2291 [inline] __mmap_new_vma mm/vma.c:2355 [inline] __mmap_region+0x1789/0x2670 mm/vma.c:2456 mmap_region+0x270/0x320 mm/mmap.c:1348 do_mmap+0xc00/0xfc0 mm/mmap.c:496 vm_mmap_pgoff+0x1ba/0x360 mm/util.c:580 ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:542 __do_sys_mmap arch/x86/kernel/sys_x86_64.c:89 [inline] __se_sys_mmap arch/x86/kernel/sys_x86_64.c:82 [inline] __x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:82 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa139185d19 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fa136ff6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007fa139375fa0 RCX: 00007fa139185d19 RDX: 8088e3ad122bc192 RSI: 0000000000600000 RDI: 0000000020000000 RBP: 00007fa139201a20 R08: 0000000000000004 R09: 0000000000000000 R10: 0000000004002011 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fa139375fa0 R15: 00007ffcfaceef38