syzbot

         option from the mount to silence this warning.
=======================================================
======================================================
WARNING: possible circular locking dependency detected
6.1.116-syzkaller #0 Not tainted
------------------------------------------------------
syz-executor352/4289 is trying to acquire lock:
ffff0000d4fb2548 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0x9c/0x124 mm/memory.c:5850

but task is already holding lock:
ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:778 [inline]
ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 fs/ntfs3/file.c:1144

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}:
       down_write+0x5c/0x88 kernel/locking/rwsem.c:1573
       inode_lock include/linux/fs.h:758 [inline]
       ntfs_file_mmap+0x4b0/0x688 fs/ntfs3/file.c:399
       call_mmap include/linux/fs.h:2270 [inline]
       mmap_region+0xdd0/0x1a98 mm/mmap.c:2763
       do_mmap+0xa00/0x1108 mm/mmap.c:1425
       vm_mmap_pgoff+0x1a4/0x2b4 mm/util.c:520
       ksys_mmap_pgoff+0x3c8/0x5b0 mm/mmap.c:1471
       __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:38 [inline]
       invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

-> #0 (&mm->mmap_lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049
       lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662
       __might_fault+0xc4/0x124 mm/memory.c:5851
       fault_in_readable+0x188/0x5f0 mm/gup.c:1891
       fault_in_iov_iter_readable+0xcc/0x22c lib/iov_iter.c:356
       generic_perform_write+0x1c8/0x55c mm/filemap.c:3835
       __generic_file_write_iter+0x168/0x388 mm/filemap.c:3973
       ntfs_file_write_iter+0x4d4/0x580 fs/ntfs3/file.c:1165
       call_write_iter include/linux/fs.h:2265 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x610/0x91c fs/read_write.c:584
       ksys_write+0x15c/0x26c fs/read_write.c:637
       __do_sys_write fs/read_write.c:649 [inline]
       __se_sys_write fs/read_write.c:646 [inline]
       __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
       __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
       invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
       el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
       do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
       el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
       el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
       el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&sb->s_type->i_mutex_key#17);
                               lock(&mm->mmap_lock);
                               lock(&sb->s_type->i_mutex_key#17);
  lock(&mm->mmap_lock);

 *** DEADLOCK ***

3 locks held by syz-executor352/4289:
 #0: ffff0000d82cdc68 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x124/0x16c fs/file.c:1031
 #1: ffff0000da4e2460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x244/0x91c fs/read_write.c:580
 #2: ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: inode_trylock include/linux/fs.h:778 [inline]
 #2: ffff0000e5007240 (&sb->s_type->i_mutex_key#17){+.+.}-{3:3}, at: ntfs_file_write_iter+0x190/0x580 fs/ntfs3/file.c:1144

stack backtrace:
CPU: 1 PID: 4289 Comm: syz-executor352 Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2048
 check_noncircular+0x2cc/0x378 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 kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049
 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662
 __might_fault+0xc4/0x124 mm/memory.c:5851
 fault_in_readable+0x188/0x5f0 mm/gup.c:1891
 fault_in_iov_iter_readable+0xcc/0x22c lib/iov_iter.c:356
 generic_perform_write+0x1c8/0x55c mm/filemap.c:3835
 __generic_file_write_iter+0x168/0x388 mm/filemap.c:3973
 ntfs_file_write_iter+0x4d4/0x580 fs/ntfs3/file.c:1165
 call_write_iter include/linux/fs.h:2265 [inline]
 new_sync_write fs/read_write.c:491 [inline]
 vfs_write+0x610/0x91c fs/read_write.c:584
 ksys_write+0x15c/0x26c fs/read_write.c:637
 __do_sys_write fs/read_write.c:649 [inline]
 __se_sys_write fs/read_write.c:646 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:646
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585