syzbot

======================================================
WARNING: possible circular locking dependency detected
6.7.0-rc1-syzkaller-00012-g9bacdd8996c7 #0 Not tainted
------------------------------------------------------
syz-executor106/5073 is trying to acquire lock:
ffff888079be4360 (&ni->ni_lock#2/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
ffff888079be4360 (&ni->ni_lock#2/4){+.+.}-{3:3}, at: attr_data_get_block+0x46d/0x2da0 fs/ntfs3/attrib.c:918

but task is already holding lock:
ffff88804a17d720 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
ffff88804a17d720 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x181/0x420 mm/util.c:544

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&mm->mmap_lock){++++}-{3:3}:
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5753
       __might_fault+0xc1/0x120 mm/memory.c:5955
       _copy_to_user+0x2a/0xa0 lib/usercopy.c:36
       copy_to_user include/linux/uaccess.h:191 [inline]
       fiemap_fill_next_extent+0x235/0x410 fs/ioctl.c:145
       ni_fiemap+0x100b/0x1230 fs/ntfs3/frecord.c:1948
       ntfs_fiemap+0x132/0x180 fs/ntfs3/file.c:1164
       ioctl_fiemap fs/ioctl.c:220 [inline]
       do_vfs_ioctl+0x19ea/0x2b40 fs/ioctl.c:811
       __do_sys_ioctl fs/ioctl.c:869 [inline]
       __se_sys_ioctl+0x81/0x170 fs/ioctl.c:857
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

-> #0 (&ni->ni_lock#2/4){+.+.}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain+0x18e4/0x59f0 kernel/locking/lockdep.c:3868
       __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5136
       lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5753
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
       ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
       attr_data_get_block+0x46d/0x2da0 fs/ntfs3/attrib.c:918
       ntfs_file_mmap+0x453/0x7a0 fs/ntfs3/file.c:292
       call_mmap include/linux/fs.h:2025 [inline]
       mmap_region+0xf47/0x1fa0 mm/mmap.c:2851
       do_mmap+0x76b/0xde0 mm/mmap.c:1379
       vm_mmap_pgoff+0x1e2/0x420 mm/util.c:546
       ksys_mmap_pgoff+0x4ff/0x6d0 mm/mmap.c:1425
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82
       entry_SYSCALL_64_after_hwframe+0x63/0x6b

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&mm->mmap_lock);
                               lock(&ni->ni_lock#2/4);
                               lock(&mm->mmap_lock);
  lock(&ni->ni_lock#2/4);

 *** DEADLOCK ***

1 lock held by syz-executor106/5073:
 #0: ffff88804a17d720 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:124 [inline]
 #0: ffff88804a17d720 (&mm->mmap_lock){++++}-{3:3}, at: vm_mmap_pgoff+0x181/0x420 mm/util.c:544

stack backtrace:
CPU: 0 PID: 5073 Comm: syz-executor106 Not tainted 6.7.0-rc1-syzkaller-00012-g9bacdd8996c7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/09/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_noncircular+0x366/0x490 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain+0x18e4/0x59f0 kernel/locking/lockdep.c:3868
 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5136
 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5753
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
 ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
 attr_data_get_block+0x46d/0x2da0 fs/ntfs3/attrib.c:918
 ntfs_file_mmap+0x453/0x7a0 fs/ntfs3/file.c:292
 call_mmap include/linux/fs.h:2025 [inline]
 mmap_region+0xf47/0x1fa0 mm/mmap.c:2851
 do_mmap+0x76b/0xde0 mm/mmap.c:1379
 vm_mmap_pgoff+0x1e2/0x420 mm/util.c:546
 ksys_mmap_pgoff+0x4ff/0x6d0 mm/mmap.c:1425
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x45/0x110 arch/x86/entry/common.c:82
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f44f880c639
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f44f87a8208 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f44f88b3618 RCX: 00007f44f880c639
RDX: 00000000027fffff RSI: 0000000000600000 RDI: 0000000020000000
RBP: 00007f44f88b3610 R08: 0000000000000004 R09: 0000000000000000
R10: 0000000004002011 R11: 0000000000000246 R12: 00007f44f887fb5c
R13: 00007f44f88600c0 R14: 6465646165726874 R15: 0030656c69662f2e
 </TASK>