ntfs3(loop3): ino=18, mi_enum_attr ntfs3(loop3): Mark volume as dirty due to NTFS errors ntfs3(loop3): ino=1a, mi_enum_attr ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.3.878/14796 is trying to acquire lock: ffff88805fbb88a0 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ffff88805fbb88a0 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7ca/0x10b0 fs/ntfs3/file.c:644 but task is already holding lock: ffff88805fbb8d28 (mapping.invalidate_lock#13){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1034 [inline] ffff88805fbb8d28 (mapping.invalidate_lock#13){++++}-{4:4}, at: ntfs_fallocate+0x3be/0x10b0 fs/ntfs3/file.c:574 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (mapping.invalidate_lock#13){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 filemap_invalidate_lock_shared include/linux/fs.h:1044 [inline] filemap_fault+0x5d9/0x12c0 mm/filemap.c:3477 __do_fault+0x138/0x390 mm/memory.c:5280 do_read_fault mm/memory.c:5698 [inline] do_fault mm/memory.c:5832 [inline] do_pte_missing mm/memory.c:4361 [inline] handle_pte_fault mm/memory.c:6177 [inline] __handle_mm_fault mm/memory.c:6318 [inline] handle_mm_fault+0x23c6/0x3400 mm/memory.c:6487 faultin_page mm/gup.c:1126 [inline] __get_user_pages+0x1685/0x2860 mm/gup.c:1428 populate_vma_page_range+0x29f/0x3a0 mm/gup.c:1860 __mm_populate+0x24c/0x380 mm/gup.c:1963 mm_populate include/linux/mm.h:3466 [inline] vm_mmap_pgoff+0x38a/0x4d0 mm/util.c:585 ksys_mmap_pgoff+0x4e9/0x720 mm/mmap.c:604 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&mm->mmap_lock){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __might_fault+0xcc/0x130 mm/memory.c:7081 _inline_copy_to_user include/linux/uaccess.h:192 [inline] _copy_to_user+0x2c/0xb0 lib/usercopy.c:26 copy_to_user include/linux/uaccess.h:225 [inline] fiemap_fill_next_extent+0x1c0/0x390 fs/ioctl.c:144 ni_fiemap+0x391/0xbf0 fs/ntfs3/frecord.c:1896 ntfs_fiemap+0x11d/0x1a0 fs/ntfs3/file.c:1354 ioctl_fiemap fs/ioctl.c:219 [inline] do_vfs_ioctl+0x1188/0x1440 fs/ioctl.c:531 __do_sys_ioctl fs/ioctl.c:595 [inline] __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ni->ni_lock#3/5){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ntfs_fallocate+0x7ca/0x10b0 fs/ntfs3/file.c:644 vfs_fallocate+0x672/0x7f0 fs/open.c:342 ksys_fallocate fs/open.c:366 [inline] __do_sys_fallocate fs/open.c:371 [inline] __se_sys_fallocate fs/open.c:369 [inline] __x64_sys_fallocate+0xc0/0x110 fs/open.c:369 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f other info that might help us debug this: Chain exists of: &ni->ni_lock#3/5 --> &mm->mmap_lock --> mapping.invalidate_lock#13 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#13); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#13); lock(&ni->ni_lock#3/5); *** DEADLOCK *** 3 locks held by syz.3.878/14796: #0: ffff88801c710480 (sb_writers#23){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3110 [inline] #0: ffff88801c710480 (sb_writers#23){.+.+}-{0:0}, at: vfs_fallocate+0x5f9/0x7f0 fs/open.c:341 #1: ffff88805fbb8b58 (&sb->s_type->i_mutex_key#28){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:979 [inline] #1: ffff88805fbb8b58 (&sb->s_type->i_mutex_key#28){+.+.}-{4:4}, at: ntfs_fallocate+0x2f1/0x10b0 fs/ntfs3/file.c:560 #2: ffff88805fbb8d28 (mapping.invalidate_lock#13){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1034 [inline] #2: ffff88805fbb8d28 (mapping.invalidate_lock#13){++++}-{4:4}, at: ntfs_fallocate+0x3be/0x10b0 fs/ntfs3/file.c:574 stack backtrace: CPU: 0 UID: 0 PID: 14796 Comm: syz.3.878 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:535 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:547 ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] ntfs_fallocate+0x7ca/0x10b0 fs/ntfs3/file.c:644 vfs_fallocate+0x672/0x7f0 fs/open.c:342 ksys_fallocate fs/open.c:366 [inline] __do_sys_fallocate fs/open.c:371 [inline] __se_sys_fallocate fs/open.c:369 [inline] __x64_sys_fallocate+0xc0/0x110 fs/open.c:369 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f6e5c0ceec9 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:00007f6e5a336038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d RAX: ffffffffffffffda RBX: 00007f6e5c325fa0 RCX: 00007f6e5c0ceec9 RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000005 RBP: 00007f6e5c151f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000002000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f6e5c326038 R14: 00007f6e5c325fa0 R15: 00007ffd1d654d48