====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.5.2264/18801 is trying to acquire lock: ffff888065270270 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff8880459688f8 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_set_size+0x119/0x220 fs/ntfs3/inode.c:860 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->file.run_lock#2){++++}-{4:4}: down_read+0x9b/0x480 kernel/locking/rwsem.c:1537 run_unpack_ex+0x671/0x740 fs/ntfs3/run.c:1124 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0xd97/0x3a90 fs/ntfs3/inode.c:541 ntfs_dir_emit fs/ntfs3/dir.c:337 [inline] ntfs_read_hdr+0x8dd/0xaf0 fs/ntfs3/dir.c:385 ntfs_readdir+0x6cd/0x10b0 fs/ntfs3/dir.c:496 iterate_dir+0x296/0xaf0 fs/readdir.c:108 __do_sys_getdents fs/readdir.c:326 [inline] __se_sys_getdents fs/readdir.c:312 [inline] __x64_sys_getdents+0x13c/0x2b0 fs/readdir.c:312 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xfa0 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 kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x126f/0x1c90 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825 down_write_nested+0x96/0x210 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x3ff/0x6f0 fs/ntfs3/attrib.c:159 attr_set_size+0x15ae/0x2c50 fs/ntfs3/attrib.c:574 ntfs_set_size+0x13d/0x220 fs/ntfs3/inode.c:862 ntfs_extend+0x7c2/0xa20 fs/ntfs3/file.c:387 ntfs_file_write_iter+0x2ff/0x2120 fs/ntfs3/file.c:1248 iter_file_splice_write+0xa24/0x12e0 fs/splice.c:738 ntfs_file_splice_write+0x71/0xa0 fs/ntfs3/file.c:1375 do_splice_from fs/splice.c:938 [inline] direct_splice_actor+0x192/0x6c0 fs/splice.c:1161 splice_direct_to_actor+0x345/0xa30 fs/splice.c:1105 do_splice_direct_actor fs/splice.c:1204 [inline] do_splice_direct+0x174/0x240 fs/splice.c:1230 do_sendfile+0xb06/0xe50 fs/read_write.c:1370 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64 fs/read_write.c:1417 [inline] __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xfa0 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.5.2264/18801: #0: ffff888065272420 (sb_writers#25){.+.+}-{0:0}, at: splice_direct_to_actor+0x345/0xa30 fs/splice.c:1105 #1: ffff888045968ae0 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:1010 [inline] #1: ffff888045968ae0 (&sb->s_type->i_mutex_key#34){+.+.}-{4:4}, at: ntfs_file_write_iter+0xdf/0x2120 fs/ntfs3/file.c:1216 #2: ffff888045968848 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline] #2: ffff888045968848 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_set_size+0x111/0x220 fs/ntfs3/inode.c:859 #3: ffff8880459688f8 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_set_size+0x119/0x220 fs/ntfs3/inode.c:860 stack backtrace: CPU: 1 UID: 0 PID: 18801 Comm: syz.5.2264 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2043 check_noncircular+0x14c/0x170 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+0x126f/0x1c90 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825 down_write_nested+0x96/0x210 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x3ff/0x6f0 fs/ntfs3/attrib.c:159 attr_set_size+0x15ae/0x2c50 fs/ntfs3/attrib.c:574 ntfs_set_size+0x13d/0x220 fs/ntfs3/inode.c:862 ntfs_extend+0x7c2/0xa20 fs/ntfs3/file.c:387 ntfs_file_write_iter+0x2ff/0x2120 fs/ntfs3/file.c:1248 iter_file_splice_write+0xa24/0x12e0 fs/splice.c:738 ntfs_file_splice_write+0x71/0xa0 fs/ntfs3/file.c:1375 do_splice_from fs/splice.c:938 [inline] direct_splice_actor+0x192/0x6c0 fs/splice.c:1161 splice_direct_to_actor+0x345/0xa30 fs/splice.c:1105 do_splice_direct_actor fs/splice.c:1204 [inline] do_splice_direct+0x174/0x240 fs/splice.c:1230 do_sendfile+0xb06/0xe50 fs/read_write.c:1370 __do_sys_sendfile64 fs/read_write.c:1431 [inline] __se_sys_sendfile64 fs/read_write.c:1417 [inline] __x64_sys_sendfile64+0x1d8/0x220 fs/read_write.c:1417 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7facff98f6c9 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:00007fad008fb038 EFLAGS: 00000246 ORIG_RAX: 0000000000000028 RAX: ffffffffffffffda RBX: 00007facffbe5fa0 RCX: 00007facff98f6c9 RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000005 RBP: 00007facffa11f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000020fffe82 R11: 0000000000000246 R12: 0000000000000000 R13: 00007facffbe6038 R14: 00007facffbe5fa0 R15: 00007fff8b3a4348