loop5: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc2-syzkaller-00162-g41687a5c6f8b #0 Not tainted ------------------------------------------------------ syz.5.3063/14864 is trying to acquire lock: ffff888047477680 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] ffff888047477680 (&ni->ni_lock/5){+.+.}-{4:4}, at: attr_data_get_block+0x303/0x1d10 fs/ntfs3/attrib.c:918 but task is already holding lock: ffff88807b5757e0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] ffff88807b5757e0 (&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}: __might_fault mm/memory.c:6991 [inline] __might_fault+0x113/0x190 mm/memory.c:6985 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2d/0xd0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x239/0x390 fs/ioctl.c:145 ni_fiemap+0x94e/0xbf0 fs/ntfs3/frecord.c:1985 ntfs_fiemap+0xc8/0x110 fs/ntfs3/file.c:1290 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x404/0x1a60 fs/ioctl.c:841 __do_sys_ioctl fs/ioctl.c:905 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __x64_sys_ioctl+0x114/0x210 fs/ioctl.c:893 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 (&ni->ni_lock/5){+.+.}-{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 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] attr_data_get_block+0x303/0x1d10 fs/ntfs3/attrib.c:918 ntfs_file_mmap+0x575/0x780 fs/ntfs3/file.c:305 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(&ni->ni_lock/5); lock(&mm->mmap_lock); lock(&ni->ni_lock/5); *** DEADLOCK *** 1 lock held by syz.5.3063/14864: #0: ffff88807b5757e0 (&mm->mmap_lock){++++}-{4:4}, at: mmap_write_lock_killable include/linux/mmap_lock.h:374 [inline] #0: ffff88807b5757e0 (&mm->mmap_lock){++++}-{4:4}, at: vm_mmap_pgoff+0x1d8/0x450 mm/util.c:577 stack backtrace: CPU: 1 UID: 0 PID: 14864 Comm: syz.5.3063 Not tainted 6.16.0-rc2-syzkaller-00162-g41687a5c6f8b #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 __mutex_lock_common kernel/locking/mutex.c:602 [inline] __mutex_lock+0x199/0xb90 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] attr_data_get_block+0x303/0x1d10 fs/ntfs3/attrib.c:918 ntfs_file_mmap+0x575/0x780 fs/ntfs3/file.c:305 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:0x7f3a8a78e929 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:00007f3a8b691038 EFLAGS: 00000246 ORIG_RAX: 0000000000000009 RAX: ffffffffffffffda RBX: 00007f3a8a9b5fa0 RCX: 00007f3a8a78e929 RDX: 000000000000000e RSI: 0000000000001000 RDI: 0000200000001000 RBP: 00007f3a8a810b39 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000000000011 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f3a8a9b5fa0 R15: 00007ffce72f6028