ntfs3(loop7): Failed to initialize $Extend/$ObjId. ====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc3-syzkaller #0 Not tainted ------------------------------------------------------ syz.7.1771/10919 is trying to acquire lock: ffff88805af60af0 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline] ffff88805af60af0 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: ntfs_file_mmap+0x60c/0x780 fs/ntfs3/file.c:313 but task is already holding lock: ffff88807bd8cd20 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] ffff88807bd8cd20 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1d8/0x450 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+0x1687/0x29e0 mm/gup.c:3341 pin_user_pages_fast+0xa7/0xf0 mm/gup.c:3463 iov_iter_extract_user_pages lib/iov_iter.c:1846 [inline] iov_iter_extract_pages+0x3a2/0x1ed0 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+0x2f00/0x4180 fs/direct-io.c:1243 blockdev_direct_IO include/linux/fs.h:3477 [inline] ntfs_direct_IO+0x23c/0x4e0 fs/ntfs3/inode.c:813 generic_file_direct_write+0x19a/0x410 mm/filemap.c:4046 __generic_file_write_iter+0x11b/0x240 mm/filemap.c:4215 ntfs_file_write_iter+0xed3/0x2120 fs/ntfs3/file.c:1197 do_iter_readv_writev+0x657/0x950 fs/read_write.c:827 vfs_writev+0x35f/0xde0 fs/read_write.c:1057 do_pwritev+0x1a6/0x270 fs/read_write.c:1153 __do_sys_pwritev2 fs/read_write.c:1211 [inline] __se_sys_pwritev2 fs/read_write.c:1202 [inline] __x64_sys_pwritev2+0xef/0x160 fs/read_write.c:1202 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&sb->s_type->i_mutex_key#20){+.+.}-{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+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:869 [inline] ntfs_file_mmap+0x60c/0x780 fs/ntfs3/file.c:313 call_mmap include/linux/fs.h:2286 [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+0x128e/0x25e0 mm/vma.c:2622 mmap_region+0x32b/0x3f0 mm/vma.c:2692 do_mmap+0xa3e/0x1210 mm/mmap.c:561 vm_mmap_pgoff+0x281/0x450 mm/util.c:579 ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:607 __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/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 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#20); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#20); *** DEADLOCK *** 1 lock held by syz.7.1771/10919: #0: ffff88807bd8cd20 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] #0: ffff88807bd8cd20 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1d8/0x450 mm/util.c:577 stack backtrace: CPU: 0 UID: 0 PID: 10919 Comm: syz.7.1771 Not tainted 6.16.0-rc3-syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2046 check_noncircular+0x14c/0x170 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+0x126f/0x1c90 kernel/locking/lockdep.c:5240 lock_acquire kernel/locking/lockdep.c:5871 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5828 down_write+0x92/0x200 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:869 [inline] ntfs_file_mmap+0x60c/0x780 fs/ntfs3/file.c:313 call_mmap include/linux/fs.h:2286 [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+0x128e/0x25e0 mm/vma.c:2622 mmap_region+0x32b/0x3f0 mm/vma.c:2692 do_mmap+0xa3e/0x1210 mm/mmap.c:561 vm_mmap_pgoff+0x281/0x450 mm/util.c:579 ksys_mmap_pgoff+0x32c/0x5c0 mm/mmap.c:607 __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/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7ff05298e929 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:00007ff0538a7038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007ff052bb5fa0 RCX: 00007ff05298e929 RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000200000000000 RBP: 00007ff052a10b39 R08: 0000000000000004 R09: 0000000000000000 R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007ff052bb5fa0 R15: 00007ffc30ff4af8