======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Tainted: G             L     
------------------------------------------------------
syz.7.884/10456 is trying to acquire lock:
ffff888069ac4278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x610/0xba0 fs/ntfs3/run.c:1105

but task is already holding lock:
ffff888066023bf0 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x37a/0x15f0 fs/ntfs3/attrib.c:1902

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+0x47/0x2e0 kernel/locking/rwsem.c:1537
       run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1135
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x238b/0x3860 fs/ntfs3/inode.c:542
       dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264
       ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85
       lookup_open fs/namei.c:4412 [inline]
       open_last_lookups fs/namei.c:4539 [inline]
       path_openat+0x119c/0x3840 fs/namei.c:4783
       do_filp_open+0x1fa/0x410 fs/namei.c:4813
       do_sys_openat2+0x121/0x200 fs/open.c:1391
       do_sys_open fs/open.c:1397 [inline]
       __do_sys_openat fs/open.c:1413 [inline]
       __se_sys_openat fs/open.c:1408 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1408
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/0xf80 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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
       lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868
       down_read_nested+0x49/0x2e0 kernel/locking/rwsem.c:1662
       run_unpack_ex+0x610/0xba0 fs/ntfs3/run.c:1105
       attr_load_runs fs/ntfs3/attrib.c:81 [inline]
       attr_collapse_range+0xb83/0x15f0 fs/ntfs3/attrib.c:1970
       ntfs_fallocate+0x7d6/0x10b0 fs/ntfs3/file.c:690
       vfs_fallocate+0x669/0x7e0 fs/open.c:339
       ksys_fallocate fs/open.c:363 [inline]
       __do_sys_fallocate fs/open.c:368 [inline]
       __se_sys_fallocate fs/open.c:366 [inline]
       __x64_sys_fallocate+0xc0/0x110 fs/open.c:366
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/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(&ni->file.run_lock#2);
                               lock(&wnd->rw_lock);
                               lock(&ni->file.run_lock#2);
  rlock(&wnd->rw_lock);

 *** DEADLOCK ***

5 locks held by syz.7.884/10456:
 #0: ffff888069ac6420 (sb_writers#15){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2680 [inline]
 #0: ffff888069ac6420 (sb_writers#15){.+.+}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0 fs/open.c:338
 #1: ffff888066023dd8 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1028 [inline]
 #1: ffff888066023dd8 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: ntfs_fallocate+0x2ee/0x10b0 fs/ntfs3/file.c:605
 #2: ffff888066023f78 (mapping.invalidate_lock#9){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1083 [inline]
 #2: ffff888066023f78 (mapping.invalidate_lock#9){++++}-{4:4}, at: ntfs_fallocate+0x3b8/0x10b0 fs/ntfs3/file.c:619
 #3: ffff888066023b40 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1128 [inline]
 #3: ffff888066023b40 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7c4/0x10b0 fs/ntfs3/file.c:689
 #4: ffff888066023bf0 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x37a/0x15f0 fs/ntfs3/attrib.c:1902

stack backtrace:
CPU: 0 UID: 0 PID: 10456 Comm: syz.7.884 Tainted: G             L      syzkaller #0 PREEMPT(full) 
Tainted: [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2e2/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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237
 lock_acquire+0x117/0x340 kernel/locking/lockdep.c:5868
 down_read_nested+0x49/0x2e0 kernel/locking/rwsem.c:1662
 run_unpack_ex+0x610/0xba0 fs/ntfs3/run.c:1105
 attr_load_runs fs/ntfs3/attrib.c:81 [inline]
 attr_collapse_range+0xb83/0x15f0 fs/ntfs3/attrib.c:1970
 ntfs_fallocate+0x7d6/0x10b0 fs/ntfs3/file.c:690
 vfs_fallocate+0x669/0x7e0 fs/open.c:339
 ksys_fallocate fs/open.c:363 [inline]
 __do_sys_fallocate fs/open.c:368 [inline]
 __se_sys_fallocate fs/open.c:366 [inline]
 __x64_sys_fallocate+0xc0/0x110 fs/open.c:366
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xf80 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd594b8f749
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:00007fd595ae2038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007fd594de5fa0 RCX: 00007fd594b8f749
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000005
RBP: 00007fd594c13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd594de6038 R14: 00007fd594de5fa0 R15: 00007ffd116ae5c8
 </TASK>