====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.4388/26531 is trying to acquire lock: ffff8880a0ba2270 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff888052cb81b0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->file.run_lock#2){++++}-{4:4}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1119 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x232b/0x37c0 fs/ntfs3/inode.c:540 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 __lookup_slow+0x297/0x3d0 fs/namei.c:1808 lookup_slow+0x53/0x70 fs/namei.c:1825 walk_component+0x2d2/0x400 fs/namei.c:2129 lookup_last fs/namei.c:2630 [inline] path_lookupat+0x163/0x430 fs/namei.c:2654 filename_lookup+0x212/0x570 fs/namei.c:2683 user_path_at+0x3a/0x60 fs/namei.c:3127 do_sys_truncate+0xa3/0x190 fs/open.c:139 __do_sys_truncate fs/open.c:153 [inline] __se_sys_truncate fs/open.c:151 [inline] __x64_sys_truncate+0x5b/0x70 fs/open.c:151 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 (&wnd->rw_lock){++++}-{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 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1296 ntfs_mkdir+0x3d/0x50 fs/ntfs3/namei.c:215 vfs_mkdir+0x306/0x510 fs/namei.c:4366 do_mkdirat+0x247/0x590 fs/namei.c:4399 __do_sys_mkdirat fs/namei.c:4416 [inline] __se_sys_mkdirat fs/namei.c:4414 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4414 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: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); *** DEADLOCK *** 5 locks held by syz.5.4388/26531: #0: ffff8880a0ba0428 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557 #1: ffff888052cbea68 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:915 [inline] #1: ffff888052cbea68 (&type->i_mutex_dir_key#17/1){+.+.}-{4:4}, at: filename_create+0x1f8/0x3c0 fs/namei.c:4139 #2: ffff888052cbe7d0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline] #2: ffff888052cbe7d0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_create_inode+0x16e/0x32a0 fs/ntfs3/inode.c:1204 #3: ffff8880a0ba2128 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x163/0xd50 fs/ntfs3/fsntfs.c:571 #4: ffff888052cb81b0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511 stack backtrace: CPU: 0 UID: 0 PID: 26531 Comm: syz.5.4388 Not tainted syzkaller #0 PREEMPT(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 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1296 ntfs_mkdir+0x3d/0x50 fs/ntfs3/namei.c:215 vfs_mkdir+0x306/0x510 fs/namei.c:4366 do_mkdirat+0x247/0x590 fs/namei.c:4399 __do_sys_mkdirat fs/namei.c:4416 [inline] __se_sys_mkdirat fs/namei.c:4414 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:4414 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:0x7ff85bb8d617 Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 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:00007ff859dede68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007ff859dedef0 RCX: 00007ff85bb8d617 RDX: 00000000000001ff RSI: 0000200000000280 RDI: 00000000ffffff9c RBP: 0000200000000140 R08: 0000200000000080 R09: 0000000000000000 R10: 0000200000000140 R11: 0000000000000246 R12: 0000200000000280 R13: 00007ff859dedeb0 R14: 0000000000000000 R15: 0000000000000000 ntfs3(loop5): ino=0, attr_set_size ntfs3(loop5): ino=0, attr_set_size