syzbot

loop1: detected capacity change from 0 to 4096
======================================================
WARNING: possible circular locking dependency detected
6.1.118-syzkaller #0 Not tainted
------------------------------------------------------
syz.1.2186/10953 is trying to acquire lock:
ffff888070e383a0 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
ffff888070e383a0 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: ntfs_file_mmap+0x583/0x7d0 fs/ntfs3/file.c:399

but task is already holding lock:
ffff88807a3ae2d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
ffff88807a3ae2d8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x175/0x2d0 mm/util.c:518

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       internal_get_user_pages_fast+0x224/0x2cf0 mm/gup.c:3031
       __iov_iter_get_pages_alloc+0x3b1/0xa70 lib/iov_iter.c:1460
       iov_iter_get_pages2+0xcb/0x120 lib/iov_iter.c:1503
       dio_refill_pages fs/direct-io.c:172 [inline]
       dio_get_page fs/direct-io.c:215 [inline]
       do_direct_IO fs/direct-io.c:932 [inline]
       __blockdev_direct_IO+0x13d6/0x4810 fs/direct-io.c:1266
       blockdev_direct_IO include/linux/fs.h:3342 [inline]
       ntfs_direct_IO+0x193/0x360 fs/ntfs3/inode.c:800
       generic_file_direct_write+0x204/0x460 mm/filemap.c:3769
       __generic_file_write_iter+0x1c4/0x400 mm/filemap.c:3929
       ntfs_file_write_iter+0x5fa/0x6d0 fs/ntfs3/file.c:1165
       do_iter_write+0x6e6/0xc40 fs/read_write.c:861
       vfs_writev fs/read_write.c:934 [inline]
       do_writev+0x27b/0x460 fs/read_write.c:977
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825
       __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
       lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
       down_write+0x36/0x60 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:758 [inline]
       ntfs_file_mmap+0x583/0x7d0 fs/ntfs3/file.c:399
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_region+0xf96/0x1fa0 mm/mmap.c:2763
       do_mmap+0x8c5/0xf60 mm/mmap.c:1425
       vm_mmap_pgoff+0x1ca/0x2d0 mm/util.c:520
       ksys_mmap_pgoff+0x4f5/0x6d0 mm/mmap.c:1471
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

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.1.2186/10953:
 #0: ffff88807a3ae2d8 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
 #0: ffff88807a3ae2d8 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x175/0x2d0 mm/util.c:518

stack backtrace:
CPU: 1 PID: 10953 Comm: syz.1.2186 Not tainted 6.1.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
 check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain+0x1661/0x5950 kernel/locking/lockdep.c:3825
 __lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5049
 lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
 down_write+0x36/0x60 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:758 [inline]
 ntfs_file_mmap+0x583/0x7d0 fs/ntfs3/file.c:399
 call_mmap include/linux/fs.h:2270 [inline]
 mmap_region+0xf96/0x1fa0 mm/mmap.c:2763
 do_mmap+0x8c5/0xf60 mm/mmap.c:1425
 vm_mmap_pgoff+0x1ca/0x2d0 mm/util.c:520
 ksys_mmap_pgoff+0x4f5/0x6d0 mm/mmap.c:1471
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f89f897e819
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:00007f89f9695038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f89f8b35fa0 RCX: 00007f89f897e819
RDX: 000000000000000b RSI: 0000000000b36000 RDI: 0000000020000000
RBP: 00007f89f89f175e R08: 0000000000000004 R09: 0000000000000000
R10: 0000000000028011 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f89f8b35fa0 R15: 00007ffea3009f08
 </TASK>