loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Mark volume as dirty due to NTFS errors
ntfs3: loop0: Failed to load $Extend.
============================================
WARNING: possible recursive locking detected
5.15.185-syzkaller #0 Not tainted
--------------------------------------------
syz.0.16/5162 is trying to acquire lock:
ffff888067a51e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
ffff888067a51e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: mi_read+0x2d0/0x590 fs/ntfs3/record.c:148

but task is already holding lock:
ffff888067a55980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
ffff888067a55980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_rename+0x70e/0xc60 fs/ntfs3/namei.c:315

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&ni->ni_lock/5);
  lock(&ni->ni_lock/5);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

6 locks held by syz.0.16/5162:
 #0: ffff88805c254460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
 #1: ffff888067a554c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
 #1: ffff888067a554c0 (&type->i_mutex_dir_key#8/1){+.+.}-{3:3}, at: do_renameat2+0x42a/0xf70 fs/namei.c:4924
 #2: ffff888067a55c20 (&sb->s_type->i_mutex_key#21/4){+.+.}-{3:3}, at: vfs_rename+0x7dc/0x10d0 fs/namei.c:4803
 #3: ffff888067a55220 (&ni->ni_lock/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1105 [inline]
 #3: ffff888067a55220 (&ni->ni_lock/6){+.+.}-{3:3}, at: ntfs_rename+0x6f8/0xc60 fs/ntfs3/namei.c:314
 #4: ffff888067a55980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
 #4: ffff888067a55980 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_rename+0x70e/0xc60 fs/ntfs3/namei.c:315
 #5: ffff88801eaa6120 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_look_free_mft+0x160/0xd30 fs/ntfs3/fsntfs.c:542

stack backtrace:
CPU: 0 PID: 5162 Comm: syz.0.16 Not tainted 5.15.185-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
 __lock_acquire+0x1227/0x7c60 kernel/locking/lockdep.c:-1
 lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x1eb/0x2390 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
 mi_read+0x2d0/0x590 fs/ntfs3/record.c:148
 mi_format_new+0x191/0x5c0 fs/ntfs3/record.c:374
 ni_add_subrecord+0xcc/0x440 fs/ntfs3/frecord.c:372
 ntfs_look_free_mft+0x6a4/0xd30 fs/ntfs3/fsntfs.c:686
 ni_create_attr_list+0x8a9/0x1210 fs/ntfs3/frecord.c:850
 ni_ins_attr_ext+0x304/0x9b0 fs/ntfs3/frecord.c:951
 ni_insert_attr fs/ntfs3/frecord.c:1105 [inline]
 ni_insert_resident fs/ntfs3/frecord.c:1479 [inline]
 ni_add_name+0x32f/0x7c0 fs/ntfs3/frecord.c:2985
 ni_rename+0x4b/0x130 fs/ntfs3/frecord.c:3025
 ntfs_rename+0x736/0xc60 fs/ntfs3/namei.c:318
 vfs_rename+0xbbf/0x10d0 fs/namei.c:4832
 do_renameat2+0xa83/0xf70 fs/namei.c:4985
 __do_sys_rename fs/namei.c:5031 [inline]
 __se_sys_rename fs/namei.c:5029 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5029
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f9ee3ad1d29
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:00007f9ee2d4a038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f9ee3cc1fa0 RCX: 00007f9ee3ad1d29
RDX: 0000000000000000 RSI: 0000000020000480 RDI: 0000000020000340
RBP: 00007f9ee3b4db08 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f9ee3cc1fa0 R15: 00007fffc575cbb8
 </TASK>