======================================================
WARNING: possible circular locking dependency detected
6.16.0-rc7-syzkaller #0 Not tainted
------------------------------------------------------
syz.0.25/6778 is trying to acquire lock:
ffff8880578a6310 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:869 [inline]
ffff8880578a6310 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: ntfs_file_mmap+0x521/0x730 fs/ntfs3/file.c:313

but task is already holding lock:
ffff8880241d1fe0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline]
ffff8880241d1fe0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1b9/0x4a0 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+0x22a/0x2200 mm/gup.c:3347
       iov_iter_extract_user_pages lib/iov_iter.c:1846 [inline]
       iov_iter_extract_pages+0x356/0x5d0 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+0x114b/0x33d0 fs/direct-io.c:1243
       blockdev_direct_IO include/linux/fs.h:3477 [inline]
       ntfs_direct_IO+0x207/0x410 fs/ntfs3/inode.c:813
       generic_file_direct_write+0x1d4/0x3e0 mm/filemap.c:4046
       __generic_file_write_iter+0x119/0x230 mm/filemap.c:4215
       ntfs_file_write_iter+0x718/0x810 fs/ntfs3/file.c:1197
       do_iter_readv_writev+0x546/0x7e0 fs/read_write.c:-1
       vfs_writev+0x316/0x960 fs/read_write.c:1057
       do_writev+0x149/0x2d0 fs/read_write.c:1103
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x86/0x2e0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x76/0x7e

-> #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+0x15bc/0x2df0 kernel/locking/lockdep.c:5240
       lock_acquire+0x11c/0x350 kernel/locking/lockdep.c:5871
       down_write+0x92/0x1f0 kernel/locking/rwsem.c:1577
       inode_lock include/linux/fs.h:869 [inline]
       ntfs_file_mmap+0x521/0x730 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 mm/vma.c:2622 [inline]
       mmap_region+0x1329/0x22c0 mm/vma.c:2692
       do_mmap+0xc96/0x1140 mm/mmap.c:561
       vm_mmap_pgoff+0x30f/0x4a0 mm/util.c:579
       ksys_mmap_pgoff+0x51b/0x760 mm/mmap.c:607
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0x86/0x2e0 arch/x86/entry/syscall_64.c:94
       entry_SYSCALL_64_after_hwframe+0x76/0x7e

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.0.25/6778:
 #0: ffff8880241d1fe0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline]
 #0: ffff8880241d1fe0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1b9/0x4a0 mm/util.c:577

stack backtrace:
CPU: 0 UID: 0 PID: 6778 Comm: syz.0.25 Not tainted 6.16.0-rc7-syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x185/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ed/0x300 kernel/locking/lockdep.c:2046
 check_noncircular+0x130/0x150 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+0x15bc/0x2df0 kernel/locking/lockdep.c:5240
 lock_acquire+0x11c/0x350 kernel/locking/lockdep.c:5871
 down_write+0x92/0x1f0 kernel/locking/rwsem.c:1577
 inode_lock include/linux/fs.h:869 [inline]
 ntfs_file_mmap+0x521/0x730 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 mm/vma.c:2622 [inline]
 mmap_region+0x1329/0x22c0 mm/vma.c:2692
 do_mmap+0xc96/0x1140 mm/mmap.c:561
 vm_mmap_pgoff+0x30f/0x4a0 mm/util.c:579
 ksys_mmap_pgoff+0x51b/0x760 mm/mmap.c:607
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x86/0x2e0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7fed4b98e9a9
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:00007fed4c7c8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007fed4bbb6080 RCX: 00007fed4b98e9a9
RDX: 0000000000000002 RSI: 0000000000b36000 RDI: 0000200000000000
RBP: 00007fed4ba10d69 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007fed4bbb6080 R15: 00007fffb0b138d8
 </TASK>