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

but task is already holding lock:
ffff888063450190 (&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}:
       down_read+0x97/0x1f0 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_slow+0x29d/0x3d0 fs/namei.c:1858
       lookup_slow+0x53/0x70 fs/namei.c:1875
       walk_component fs/namei.c:2221 [inline]
       lookup_last fs/namei.c:2722 [inline]
       path_lookupat+0x3f5/0x8c0 fs/namei.c:2746
       filename_lookup+0x212/0x570 fs/namei.c:2775
       user_path_at+0x3a/0x60 fs/namei.c:3567
       do_fchownat+0x105/0x270 fs/open.c:813
       __do_sys_chown fs/open.c:839 [inline]
       __se_sys_chown fs/open.c:837 [inline]
       __x64_sys_chown+0x82/0xa0 fs/open.c:837
       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_write_nested+0x3e/0x60 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+0x7dc/0x10b0 fs/ntfs3/file.c:645
       vfs_fallocate+0x672/0x7f0 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);
  lock(&wnd->rw_lock);

 *** DEADLOCK ***

5 locks held by syz.3.562/13788:
 #0: ffff88805ca96480 (sb_writers#21){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2682 [inline]
 #0: ffff88805ca96480 (sb_writers#21){.+.+}-{0:0}, at: vfs_fallocate+0x5f9/0x7f0 fs/open.c:338
 #1: ffff8880634503a8 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline]
 #1: ffff8880634503a8 (&sb->s_type->i_mutex_key#29){+.+.}-{4:4}, at: ntfs_fallocate+0x2f1/0x10b0 fs/ntfs3/file.c:560
 #2: ffff888063450578 (mapping.invalidate_lock#12){++++}-{4:4}, at: filemap_invalidate_lock include/linux/fs.h:1082 [inline]
 #2: ffff888063450578 (mapping.invalidate_lock#12){++++}-{4:4}, at: ntfs_fallocate+0x3be/0x10b0 fs/ntfs3/file.c:574
 #3: ffff8880634500f0 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ni_lock fs/ntfs3/ntfs_fs.h:1113 [inline]
 #3: ffff8880634500f0 (&ni->ni_lock#3/5){+.+.}-{4:4}, at: ntfs_fallocate+0x7ca/0x10b0 fs/ntfs3/file.c:644
 #4: ffff888063450190 (&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: 13788 Comm: syz.3.562 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
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_write_nested+0x3e/0x60 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+0x7dc/0x10b0 fs/ntfs3/file.c:645
 vfs_fallocate+0x672/0x7f0 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:0x7feeca85f749
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:00007feec8a9d038 EFLAGS: 00000246 ORIG_RAX: 000000000000011d
RAX: ffffffffffffffda RBX: 00007feecaab6090 RCX: 00007feeca85f749
RDX: 0000000000004000 RSI: 0000000000000008 RDI: 0000000000000005
RBP: 00007feeca8e3f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000004000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007feecaab6128 R14: 00007feecaab6090 R15: 00007fff5b7cb368
 </TASK>