====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.1718/12602 is trying to acquire lock: ffff888041e59040 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x687/0x760 fs/ntfs3/run.c:1135 but task is already holding lock: ffff88805fbec278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x438/0x760 fs/ntfs3/run.c:1116 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&wnd->rw_lock){++++}-{4:4}: down_write_nested+0x94/0x200 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xcb/0x7d0 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x3fc/0x700 fs/ntfs3/attrib.c:159 attr_set_size+0x159f/0x2d20 fs/ntfs3/attrib.c:574 ntfs_set_size+0x13d/0x220 fs/ntfs3/inode.c:863 ntfs_extend+0x7ba/0xa20 fs/ntfs3/file.c:435 ntfs_setattr+0xa2a/0xd60 fs/ntfs3/file.c:854 notify_change+0xb25/0x1330 fs/attr.c:556 do_truncate+0x1df/0x240 fs/open.c:68 vfs_truncate+0x538/0x720 fs/open.c:118 do_sys_truncate+0xee/0x190 fs/open.c:142 __do_sys_truncate fs/open.c:154 [inline] __se_sys_truncate fs/open.c:152 [inline] __x64_sys_truncate+0x54/0x80 fs/open.c:152 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #0 (&ni->file.run_lock#2){++++}-{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+0x14b8/0x2630 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x1cf/0x380 kernel/locking/lockdep.c:5825 down_read+0x99/0x460 kernel/locking/rwsem.c:1537 run_unpack_ex+0x687/0x760 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0xbb3/0x3af0 fs/ntfs3/inode.c:542 dir_search_u+0x163/0x3a0 fs/ntfs3/dir.c:265 ntfs_lookup+0x196/0x230 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x1d1/0x250 fs/namei.c:1805 __start_dirop fs/namei.c:2925 [inline] start_dirop fs/namei.c:2934 [inline] filename_unlinkat+0x275/0x730 fs/namei.c:5521 __do_sys_unlink fs/namei.c:5575 [inline] __se_sys_unlink fs/namei.c:5572 [inline] __x64_sys_unlink+0x46/0x70 fs/namei.c:5572 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x106/0xf80 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(&wnd->rw_lock); lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); rlock(&ni->file.run_lock#2); *** DEADLOCK *** 4 locks held by syz.4.1718/12602: #0: ffff88805374e420 (sb_writers#17){.+.+}-{0:0}, at: filename_unlinkat+0x1ad/0x730 fs/namei.c:5517 #1: ffff888042afe988 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline] #1: ffff888042afe988 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline] #1: ffff888042afe988 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline] #1: ffff888042afe988 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: filename_unlinkat+0x262/0x730 fs/namei.c:5521 #2: ffff888042afe6f0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1133 [inline] #2: ffff888042afe6f0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_lookup+0x189/0x230 fs/ntfs3/namei.c:84 #3: ffff88805fbec278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x438/0x760 fs/ntfs3/run.c:1116 stack backtrace: CPU: 0 UID: 0 PID: 12602 Comm: syz.4.1718 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120 print_circular_bug.cold+0x178/0x1c7 kernel/locking/lockdep.c:2043 check_noncircular+0x146/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 kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x14b8/0x2630 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x1cf/0x380 kernel/locking/lockdep.c:5825 down_read+0x99/0x460 kernel/locking/rwsem.c:1537 run_unpack_ex+0x687/0x760 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0xbb3/0x3af0 fs/ntfs3/inode.c:542 dir_search_u+0x163/0x3a0 fs/ntfs3/dir.c:265 ntfs_lookup+0x196/0x230 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x1d1/0x250 fs/namei.c:1805 __start_dirop fs/namei.c:2925 [inline] start_dirop fs/namei.c:2934 [inline] filename_unlinkat+0x275/0x730 fs/namei.c:5521 __do_sys_unlink fs/namei.c:5575 [inline] __se_sys_unlink fs/namei.c:5572 [inline] __x64_sys_unlink+0x46/0x70 fs/namei.c:5572 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f833d39bf79 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:00007f833e2b9028 EFLAGS: 00000246 ORIG_RAX: 0000000000000057 RAX: ffffffffffffffda RBX: 00007f833d616090 RCX: 00007f833d39bf79 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000200000000040 RBP: 00007f833d4327e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f833d616128 R14: 00007f833d616090 R15: 00007ffdf4201058