loop5: detected capacity change from 0 to 4096
ntfs3: loop5: Different NTFS sector size (4096) and media sector size (512).
ntfs3: loop5: Mark volume as dirty due to NTFS errors
ntfs3: loop5: Failed to initialize $Extend/$Reparse.
======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
syz.5.10646/29049 is trying to acquire lock:
ffff888078edcb70 (&ni->file.run_lock#2){++++}-{3:3}, at: run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117

but task is already holding lock:
ffff888059ace270 (&wnd->rw_lock){++++}-{3:3}, at: run_unpack_ex+0x702/0xba0 fs/ntfs3/run.c:1098

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&wnd->rw_lock){++++}-{3:3}:
       down_write_nested+0x9e/0x1f0 kernel/locking/rwsem.c:1689
       mark_as_free_ex+0x3e/0x380 fs/ntfs3/fsntfs.c:2484
       run_deallocate_ex+0x188/0x2e0 fs/ntfs3/attrib.c:122
       attr_set_size+0xeb5/0x2c60 fs/ntfs3/attrib.c:754
       ntfs_truncate fs/ntfs3/file.c:397 [inline]
       ntfs3_setattr+0x78f/0xb60 fs/ntfs3/file.c:706
       notify_change+0xb0d/0xe10 fs/attr.c:499
       do_truncate+0x19b/0x220 fs/open.c:66
       handle_truncate fs/namei.c:3291 [inline]
       do_open fs/namei.c:3636 [inline]
       path_openat+0x298c/0x3190 fs/namei.c:3789
       do_filp_open+0x1c5/0x3d0 fs/namei.c:3816
       do_sys_openat2+0x12c/0x1c0 fs/open.c:1419
       do_sys_open fs/open.c:1434 [inline]
       __do_sys_creat fs/open.c:1512 [inline]
       __se_sys_creat fs/open.c:1506 [inline]
       __x64_sys_creat+0x90/0xb0 fs/open.c:1506
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&ni->file.run_lock#2){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3869 [inline]
       __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
       lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
       down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
       run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x22e3/0x3750 fs/ntfs3/inode.c:533
       dir_search_u+0x1e0/0x2b0 fs/ntfs3/dir.c:264
       ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85
       lookup_one_qstr_excl+0x112/0x250 fs/namei.c:1609
       do_renameat2+0x43c/0xc70 fs/namei.c:4966
       __do_sys_renameat2 fs/namei.c:5058 [inline]
       __se_sys_renameat2 fs/namei.c:5055 [inline]
       __x64_sys_renameat2+0xd2/0xe0 fs/namei.c:5055
       do_syscall_x64 arch/x86/entry/common.c:51 [inline]
       do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&wnd->rw_lock);
                               lock(&ni->file.run_lock#2);
                               lock(&wnd->rw_lock);
  rlock(&ni->file.run_lock#2);

 *** DEADLOCK ***

4 locks held by syz.5.10646/29049:
 #0: ffff888067820418 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:403
 #1: ffff888078ed99d0 (&type->i_mutex_dir_key#14/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #1: ffff888078ed99d0 (&type->i_mutex_dir_key#14/1){+.+.}-{3:3}, at: do_renameat2+0x427/0xc70 fs/namei.c:4964
 #2: ffff888078ed9720 (&ni->ni_lock#3/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1124 [inline]
 #2: ffff888078ed9720 (&ni->ni_lock#3/6){+.+.}-{3:3}, at: ntfs_lookup+0xee/0x1f0 fs/ntfs3/namei.c:84
 #3: ffff888059ace270 (&wnd->rw_lock){++++}-{3:3}, at: run_unpack_ex+0x702/0xba0 fs/ntfs3/run.c:1098

stack backtrace:
CPU: 1 PID: 29049 Comm: syz.5.10646 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
 check_noncircular+0x2bd/0x3c0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3869 [inline]
 __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137
 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754
 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
 run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117
 ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
 ntfs_iget5+0x22e3/0x3750 fs/ntfs3/inode.c:533
 dir_search_u+0x1e0/0x2b0 fs/ntfs3/dir.c:264
 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85
 lookup_one_qstr_excl+0x112/0x250 fs/namei.c:1609
 do_renameat2+0x43c/0xc70 fs/namei.c:4966
 __do_sys_renameat2 fs/namei.c:5058 [inline]
 __se_sys_renameat2 fs/namei.c:5055 [inline]
 __x64_sys_renameat2+0xd2/0xe0 fs/namei.c:5055
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7a6398ebe9
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:00007f7a61bf6038 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f7a63bb5fa0 RCX: 00007f7a6398ebe9
RDX: ffffffffffffff9c RSI: 00002000000002c0 RDI: ffffffffffffff9c
RBP: 00007f7a63a11e19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000200000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7a63bb6038 R14: 00007f7a63bb5fa0 R15: 00007ffdb6741f38
 </TASK>