====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.0.62/6127 is trying to acquire lock: ffff88805e4d00f0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1214 [inline] ffff88805e4d00f0 (&ni->ni_lock/5){+.+.}-{4:4}, at: ntfs_fallocate+0x59f/0x1230 fs/ntfs3/file.c:543 but task is already holding lock: ffff88805e4d0578 (mapping.invalidate_lock#4){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1079 [inline] ffff88805e4d0578 (mapping.invalidate_lock#4){++++}-{4:4}, at: ntfs_fallocate+0x3b9/0x1230 fs/ntfs3/file.c:528 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (mapping.invalidate_lock#4){++++}-{4:4}: down_read+0x97/0x200 kernel/locking/rwsem.c:1568 filemap_invalidate_lock_shared include/linux/fs.h:1089 [inline] do_page_cache_ra mm/readahead.c:349 [inline] page_cache_ra_order+0x2b4/0x4a0 mm/readahead.c:562 do_sync_mmap_readahead+0x698/0x7b0 mm/filemap.c:3409 filemap_fault+0x790/0x13a0 mm/filemap.c:3559 __do_fault+0x138/0x2a0 mm/memory.c:5421 do_shared_fault mm/memory.c:5920 [inline] do_fault mm/memory.c:5994 [inline] do_pte_missing+0x65b/0x2940 mm/memory.c:4566 handle_pte_fault mm/memory.c:6375 [inline] __handle_mm_fault mm/memory.c:6513 [inline] handle_mm_fault+0xdc2/0x14d0 mm/memory.c:6682 do_user_addr_fault+0x75b/0x1340 arch/x86/mm/fault.c:1390 handle_page_fault arch/x86/mm/fault.c:1479 [inline] exc_page_fault+0x6a/0xc0 arch/x86/mm/fault.c:1532 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:595 filldir64+0x2b2/0x640 fs/readdir.c:368 dir_emit include/linux/fs.h:3587 [inline] ntfs_dir_emit fs/ntfs3/dir.c:344 [inline] ntfs_read_hdr+0x8fb/0xc80 fs/ntfs3/dir.c:385 ntfs_readdir+0x98e/0xf40 fs/ntfs3/dir.c:545 iterate_dir+0x3a5/0x580 fs/readdir.c:110 __do_sys_getdents64 fs/readdir.c:399 [inline] __se_sys_getdents64+0xf1/0x280 fs/readdir.c:384 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/5){+.+.}-{4:4}: check_prev_add kernel/locking/lockdep.c:3167 [inline] check_prevs_add kernel/locking/lockdep.c:3286 [inline] validate_chain kernel/locking/lockdep.c:3910 [inline] __lock_acquire+0x15a5/0x2d10 kernel/locking/lockdep.c:5239 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870 __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:1214 [inline] ntfs_fallocate+0x59f/0x1230 fs/ntfs3/file.c:543 vfs_fallocate+0x672/0x7f0 fs/open.c:338 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x64b/0x870 fs/ioctl.c:332 do_vfs_ioctl+0xc29/0x1540 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: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(mapping.invalidate_lock#4); lock(&ni->ni_lock/5); lock(mapping.invalidate_lock#4); lock(&ni->ni_lock/5); *** DEADLOCK *** 3 locks held by syz.0.62/6127: #0: ffff88803553c480 (sb_writers#15){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2733 [inline] #0: ffff88803553c480 (sb_writers#15){.+.+}-{0:0}, at: vfs_fallocate+0x5f9/0x7f0 fs/open.c:337 #1: ffff88805e4d03a8 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1024 [inline] #1: ffff88805e4d03a8 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: ntfs_fallocate+0x2e7/0x1230 fs/ntfs3/file.c:514 #2: ffff88805e4d0578 (mapping.invalidate_lock#4){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1079 [inline] #2: ffff88805e4d0578 (mapping.invalidate_lock#4){++++}-{4:4}, at: ntfs_fallocate+0x3b9/0x1230 fs/ntfs3/file.c:528 stack backtrace: CPU: 0 UID: 0 PID: 6127 Comm: syz.0.62 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e1/0x300 kernel/locking/lockdep.c:2045 check_noncircular+0x12e/0x150 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3167 [inline] check_prevs_add kernel/locking/lockdep.c:3286 [inline] validate_chain kernel/locking/lockdep.c:3910 [inline] __lock_acquire+0x15a5/0x2d10 kernel/locking/lockdep.c:5239 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5870 __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:1214 [inline] ntfs_fallocate+0x59f/0x1230 fs/ntfs3/file.c:543 vfs_fallocate+0x672/0x7f0 fs/open.c:338 ioctl_preallocate fs/ioctl.c:289 [inline] file_ioctl+0x64b/0x870 fs/ioctl.c:332 do_vfs_ioctl+0xc29/0x1540 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:0x7f23205ece59 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:00007f231e846028 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007f2320865fa0 RCX: 00007f23205ece59 RDX: 0000200000000000 RSI: 0000000040305829 RDI: 0000000000000005 RBP: 00007f2320682d6f R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f2320866038 R14: 00007f2320865fa0 R15: 00007ffeaff47cf8