====================================================== WARNING: possible circular locking dependency detected 6.16.0-rc2-syzkaller-00269-g11313e2f7812 #0 Not tainted ------------------------------------------------------ syz.3.201/7610 is trying to acquire lock: ffff88807c282270 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff88804cc781b0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_set_size+0x140/0x200 fs/ntfs3/inode.c:859 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:5871 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1524 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_one_qstr_excl_raw+0x115/0x280 fs/namei.c:1689 lookup_one_qstr_excl fs/namei.c:1711 [inline] filename_create+0x225/0x470 fs/namei.c:4149 do_symlinkat+0xbc/0x3f0 fs/namei.c:4758 __do_sys_symlink fs/namei.c:4786 [inline] __se_sys_symlink fs/namei.c:4784 [inline] __x64_sys_symlink+0x7a/0x90 fs/namei.c:4784 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:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1693 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_set_size+0x164/0x200 fs/ntfs3/inode.c:861 ntfs_extend+0x1d9/0x970 fs/ntfs3/file.c:343 ntfs_file_write_iter+0x3f4/0x820 fs/ntfs3/file.c:1192 iter_file_splice_write+0x937/0x1000 fs/splice.c:738 do_splice_from fs/splice.c:935 [inline] direct_splice_actor+0xfe/0x160 fs/splice.c:1158 splice_direct_to_actor+0x5a8/0xcc0 fs/splice.c:1102 do_splice_direct_actor fs/splice.c:1201 [inline] do_splice_direct+0x181/0x270 fs/splice.c:1227 do_sendfile+0x4da/0x7e0 fs/read_write.c:1370 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417 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 *** 4 locks held by syz.3.201/7610: #0: ffff88807c280428 (sb_writers#20){.+.+}-{0:0}, at: direct_splice_actor+0x49/0x160 fs/splice.c:1157 #1: ffff88804cc78398 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:899 [inline] #1: ffff88804cc78398 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: ntfs_file_write_iter+0x78/0x820 fs/ntfs3/file.c:1160 #2: ffff88804cc78100 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] #2: ffff88804cc78100 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_set_size+0x131/0x200 fs/ntfs3/inode.c:858 #3: ffff88804cc781b0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_set_size+0x140/0x200 fs/ntfs3/inode.c:859 stack backtrace: CPU: 0 UID: 0 PID: 7610 Comm: syz.3.201 Not tainted 6.16.0-rc2-syzkaller-00269-g11313e2f7812 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2046 check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2178 check_prev_add kernel/locking/lockdep.c:3168 [inline] check_prevs_add kernel/locking/lockdep.c:3287 [inline] validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3911 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5240 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5871 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1693 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_set_size+0x164/0x200 fs/ntfs3/inode.c:861 ntfs_extend+0x1d9/0x970 fs/ntfs3/file.c:343 ntfs_file_write_iter+0x3f4/0x820 fs/ntfs3/file.c:1192 iter_file_splice_write+0x937/0x1000 fs/splice.c:738 do_splice_from fs/splice.c:935 [inline] direct_splice_actor+0xfe/0x160 fs/splice.c:1158 splice_direct_to_actor+0x5a8/0xcc0 fs/splice.c:1102 do_splice_direct_actor fs/splice.c:1201 [inline] do_splice_direct+0x181/0x270 fs/splice.c:1227 do_sendfile+0x4da/0x7e0 fs/read_write.c:1370 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64+0x13e/0x190 fs/read_write.c:1417 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:0x7f52be98e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f52bf727038 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007f52bebb5fa0 RCX: 00007f52be98e929 RDX: 0000000000000000 RSI: 0000000000000005 RDI: 0000000000000004 RBP: 00007f52bea10b39 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000fffe82 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f52bebb5fa0 R15: 00007ffe0d2d0f48