====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.159/7713 is trying to acquire lock: ffff88805e9ecce0 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline] ffff88805e9ecce0 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_fallocate+0x54d/0xf70 fs/ntfs3/file.c:535 but task is already holding lock: ffff88805e9ed168 (mapping.invalidate_lock#4){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1079 [inline] ffff88805e9ed168 (mapping.invalidate_lock#4){++++}-{4:4}, at: ntfs_fallocate+0x3a2/0xf70 fs/ntfs3/file.c:520 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #2 (mapping.invalidate_lock#4){++++}-{4:4}: down_read+0x97/0x200 kernel/locking/rwsem.c:1574 filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] filemap_fault+0x6e0/0x13c0 mm/filemap.c:3576 __do_fault+0x138/0x2a0 mm/memory.c:5425 do_read_fault mm/memory.c:5860 [inline] do_fault mm/memory.c:5994 [inline] do_pte_missing+0x1828/0x28f0 mm/memory.c:4566 handle_pte_fault mm/memory.c:6379 [inline] __handle_mm_fault mm/memory.c:6517 [inline] handle_mm_fault+0xd28/0x13f0 mm/memory.c:6686 do_user_addr_fault+0x744/0x1340 arch/x86/mm/fault.c:1394 handle_page_fault arch/x86/mm/fault.c:1483 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 do_strncpy_from_user lib/strncpy_from_user.c:-1 [inline] strncpy_from_user+0xb7/0x2c0 lib/strncpy_from_user.c:130 do_getname+0x77/0x250 fs/namei.c:198 getname_flags fs/namei.c:230 [inline] getname include/linux/fs.h:2537 [inline] class_filename_constructor include/linux/fs.h:2564 [inline] __do_sys_mkdirat fs/namei.c:5329 [inline] __se_sys_mkdirat+0x24/0x150 fs/namei.c:5327 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #1 (&mm->mmap_lock){++++}-{4:4}: down_read_killable+0xa4/0x220 kernel/locking/rwsem.c:1599 mmap_read_lock_killable+0x1d/0x70 include/linux/mmap_lock.h:601 get_mmap_lock_carefully mm/mmap_lock.c:450 [inline] lock_mm_and_find_vma+0x2d6/0x340 mm/mmap_lock.c:501 do_user_addr_fault+0x341/0x1340 arch/x86/mm/fault.c:1366 handle_page_fault arch/x86/mm/fault.c:1483 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1536 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 filldir+0x2bd/0x630 fs/readdir.c:-1 dir_emit include/linux/fs.h:3587 [inline] ntfs_dir_emit fs/ntfs3/dir.c:346 [inline] ntfs_read_hdr+0x8a4/0xc10 fs/ntfs3/dir.c:387 ntfs_readdir+0x9ea/0xec0 fs/ntfs3/dir.c:547 iterate_dir+0x2f1/0x4e0 fs/readdir.c:110 __do_sys_getdents fs/readdir.c:319 [inline] __se_sys_getdents+0xf1/0x270 fs/readdir.c:304 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ni->ni_lock#2/5){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578 ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline] ntfs_fallocate+0x54d/0xf70 fs/ntfs3/file.c:535 vfs_fallocate+0x663/0x7f0 fs/open.c:338 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x5db/0x7e0 fs/ioctl.c:332 do_vfs_ioctl+0xc2a/0x1550 fs/ioctl.c:576 __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+0x174/0x580 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#2/5 --> &mm->mmap_lock --> mapping.invalidate_lock#4 Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#4); lock(&mm->mmap_lock); lock(mapping.invalidate_lock#4); lock(&ni->ni_lock#2/5); *** DEADLOCK *** 3 locks held by syz.5.159/7713: #0: ffff888034098500 (sb_writers#19){++++}-{0:0}, at: file_start_write include/linux/fs.h:2733 [inline] #0: ffff888034098500 (sb_writers#19){++++}-{0:0}, at: vfs_fallocate+0x5e9/0x7f0 fs/open.c:337 #1: ffff88805e9ecf98 (&sb->s_type->i_mutex_key#28){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline] #1: ffff88805e9ecf98 (&sb->s_type->i_mutex_key#28){+.+.}-{4:4}, at: ntfs_fallocate+0x2e1/0xf70 fs/ntfs3/file.c:506 #2: ffff88805e9ed168 (mapping.invalidate_lock#4){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1079 [inline] #2: ffff88805e9ed168 (mapping.invalidate_lock#4){++++}-{4:4}, at: ntfs_fallocate+0x3a2/0xf70 fs/ntfs3/file.c:520 stack backtrace: CPU: 0 UID: 0 PID: 7713 Comm: syz.5.159 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 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 kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1520/0x2ce0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 __mutex_lock_common kernel/locking/rtmutex_api.c:559 [inline] mutex_lock_nested+0x5a/0x1d0 kernel/locking/rtmutex_api.c:578 ni_lock fs/ntfs3/ntfs_fs.h:1222 [inline] ntfs_fallocate+0x54d/0xf70 fs/ntfs3/file.c:535 vfs_fallocate+0x663/0x7f0 fs/open.c:338 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x5db/0x7e0 fs/ioctl.c:332 do_vfs_ioctl+0xc2a/0x1550 fs/ioctl.c:576 __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+0x174/0x580 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fbfbe07e0d9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fbfbc2b5028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fbfbe306090 RCX: 00007fbfbe07e0d9 RDX: 00002000000000c0 RSI: 0000000040305829 RDI: 0000000000000006 RBP: 00007fbfbe115024 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007fbfbe306128 R14: 00007fbfbe306090 R15: 00007ffd818e17d8