======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.3.8070/4777 is trying to acquire lock:
ffff888025b72270 (&wnd->rw_lock){++++}-{4:4}, at: mark_as_free_ex+0x3e/0x390 fs/ntfs3/fsntfs.c:2464

but task is already holding lock:
ffff888055ad7630 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x38c/0x1730 fs/ntfs3/attrib.c:1904

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:5868
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537
       run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1124
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x232b/0x37e0 fs/ntfs3/inode.c:541
       dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264
       ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85
       lookup_open fs/namei.c:3774 [inline]
       open_last_lookups fs/namei.c:3895 [inline]
       path_openat+0x1101/0x3830 fs/namei.c:4131
       do_filp_open+0x1fa/0x410 fs/namei.c:4161
       do_sys_openat2+0x121/0x1c0 fs/open.c:1437
       do_sys_open fs/open.c:1452 [inline]
       __do_sys_openat fs/open.c:1468 [inline]
       __se_sys_openat fs/open.c:1463 [inline]
       __x64_sys_openat+0x138/0x170 fs/open.c:1463
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/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+0xb9b/0x2140 kernel/locking/lockdep.c:3908
       __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
       lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
       down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1706
       mark_as_free_ex+0x3e/0x390 fs/ntfs3/fsntfs.c:2464
       run_deallocate_ex+0x187/0x2f0 fs/ntfs3/attrib.c:122
       attr_collapse_range+0xc36/0x1730 fs/ntfs3/attrib.c:1972
       ntfs_fallocate+0x7d6/0x10b0 fs/ntfs3/file.c:645
       vfs_fallocate+0x669/0x7e0 fs/open.c:342
       ksys_fallocate fs/open.c:366 [inline]
       __do_sys_fallocate fs/open.c:371 [inline]
       __se_sys_fallocate fs/open.c:369 [inline]
       __x64_sys_fallocate+0xc0/0x110 fs/open.c:369
       do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
       do_syscall_64+0xfa/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 ***

5 locks held by syz.3.8070/4777:
 #0: ffff88805bcfa420 (sb_writers#18){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:3111 [inline]
 #0: ffff88805bcfa420 (sb_writers#18){.+.+}-{0:0}, at: vfs_fallocate+0x5f0/0x7e0 fs/open.c:341
 #1: ffff888055ad7818 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:980 [inline]
 #1: ffff888055ad7818 (&sb->s_type->i_mutex_key#26){+.+.}-{4:4}, at: ntfs_fallocate+0x2ee/0x10b0 fs/ntfs3/file.c:560
 #2: ffff888055ad79b8 (mapping.invalidate_lock#12){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1035 [inline]
 #2: ffff888055ad79b8 (mapping.invalidate_lock#12){++++}-{4:4}, at: ntfs_fallocate+0x3b8/0x10b0 fs/ntfs3/file.c:574
 #3: ffff888055ad7580 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
 #3: ffff888055ad7580 (&ni->ni_lock#2/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7c4/0x10b0 fs/ntfs3/file.c:644
 #4: ffff888055ad7630 (&ni->file.run_lock#2){++++}-{4:4}, at: attr_collapse_range+0x38c/0x1730 fs/ntfs3/attrib.c:1904

stack backtrace:
CPU: 1 UID: 0 PID: 4777 Comm: syz.3.8070 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043
 check_noncircular+0x134/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+0xb9b/0x2140 kernel/locking/lockdep.c:3908
 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237
 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868
 down_write_nested+0x9d/0x200 kernel/locking/rwsem.c:1706
 mark_as_free_ex+0x3e/0x390 fs/ntfs3/fsntfs.c:2464
 run_deallocate_ex+0x187/0x2f0 fs/ntfs3/attrib.c:122
 attr_collapse_range+0xc36/0x1730 fs/ntfs3/attrib.c:1972
 ntfs_fallocate+0x7d6/0x10b0 fs/ntfs3/file.c:645
 vfs_fallocate+0x669/0x7e0 fs/open.c:342
 ksys_fallocate fs/open.c:366 [inline]
 __do_sys_fallocate fs/open.c:371 [inline]
 __se_sys_fallocate fs/open.c:369 [inline]
 __x64_sys_fallocate+0xc0/0x110 fs/open.c:369
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff0be58efc9
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:00007ff0bf465038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007ff0be7e5fa0 RCX: 00007ff0be58efc9
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000005
RBP: 00007ff0be611f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ff0be7e6038 R14: 00007ff0be7e5fa0 R15: 00007ffdc5ff9058
 </TASK>