====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.6.594/11462 is trying to acquire lock: ffff8880503610f0 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135 but task is already holding lock: ffff88801b33c258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x732/0xb90 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+0x3e/0x60 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xd9/0x650 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1bd/0x6b0 fs/ntfs3/attrib.c:159 attr_set_size+0x14cf/0x2cf0 fs/ntfs3/attrib.c:574 ntfs_set_size+0x164/0x200 fs/ntfs3/inode.c:863 ntfs_extend+0x1d9/0x9c0 fs/ntfs3/file.c:435 ntfs_file_write_iter+0x424/0x870 fs/ntfs3/file.c:1314 iter_file_splice_write+0x9a0/0x1100 fs/splice.c:738 do_splice_from fs/splice.c:938 [inline] direct_splice_actor+0x104/0x160 fs/splice.c:1161 splice_direct_to_actor+0x545/0xc80 fs/splice.c:1105 do_splice_direct_actor fs/splice.c:1204 [inline] do_splice_direct+0x19b/0x2a0 fs/splice.c:1230 do_sendfile+0x547/0x7e0 fs/read_write.c:1372 __do_sys_sendfile64 fs/read_write.c:1433 [inline] __se_sys_sendfile64+0x144/0x1a0 fs/read_write.c:1419 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/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+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x2416/0x38f0 fs/ntfs3/inode.c:542 dir_search_u+0x1fd/0x2e0 fs/ntfs3/dir.c:265 ntfs_lookup+0x100/0x1d0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x131/0x360 fs/namei.c:1805 __start_dirop fs/namei.c:2925 [inline] start_dirop fs/namei.c:2934 [inline] filename_create+0x20e/0x370 fs/namei.c:4922 filename_mknodat+0x18c/0x670 fs/namei.c:5130 __do_sys_mknodat fs/namei.c:5173 [inline] __se_sys_mknodat+0x3b/0x150 fs/namei.c:5169 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/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.6.594/11462: #0: ffff888067e2a480 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:493 #1: ffff8880406cd838 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1073 [inline] #1: ffff8880406cd838 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2923 [inline] #1: ffff8880406cd838 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2934 [inline] #1: ffff8880406cd838 (&type->i_mutex_dir_key#11/1){+.+.}-{4:4}, at: filename_create+0x200/0x370 fs/namei.c:4922 #2: ffff8880406cd580 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline] #2: ffff8880406cd580 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_lookup+0xf3/0x1d0 fs/ntfs3/namei.c:84 #3: ffff88801b33c258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x732/0xb90 fs/ntfs3/run.c:1116 stack backtrace: CPU: 0 UID: 0 PID: 11462 Comm: syz.6.594 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/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+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x330 kernel/locking/lockdep.c:5868 down_read+0x97/0x200 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7fa/0xb90 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x2416/0x38f0 fs/ntfs3/inode.c:542 dir_search_u+0x1fd/0x2e0 fs/ntfs3/dir.c:265 ntfs_lookup+0x100/0x1d0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x131/0x360 fs/namei.c:1805 __start_dirop fs/namei.c:2925 [inline] start_dirop fs/namei.c:2934 [inline] filename_create+0x20e/0x370 fs/namei.c:4922 filename_mknodat+0x18c/0x670 fs/namei.c:5130 __do_sys_mknodat fs/namei.c:5173 [inline] __se_sys_mknodat+0x3b/0x150 fs/namei.c:5169 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f45d79bbf79 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:00007f45d5c0e028 EFLAGS: 00000246 ORIG_RAX: 0000000000000103 RAX: ffffffffffffffda RBX: 00007f45d7c35fa0 RCX: 00007f45d79bbf79 RDX: 0000000000000001 RSI: 00002000000001c0 RDI: 0000000000000006 RBP: 00007f45d7a527e0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000007fff R11: 0000000000000246 R12: 0000000000000000 R13: 00007f45d7c36038 R14: 00007f45d7c35fa0 R15: 00007ffe2692c928 ntfs3(loop6): ino=1e, mi_enum_attr ntfs3(loop6): ino=1e, mi_enum_attr