ntfs3: loop3: Mark volume as dirty due to NTFS errors
============================================
WARNING: possible recursive locking detected
5.15.178-syzkaller #0 Not tainted
--------------------------------------------
syz.3.305/5857 is trying to acquire lock:
ffff0000e87e1e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
ffff0000e87e1e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: mi_read+0x26c/0x4d8 fs/ntfs3/record.c:148

but task is already holding lock:
ffff0000e87e6fa0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
ffff0000e87e6fa0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_rename+0x594/0xb10 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.3.305/5857:
 #0: ffff0000eb03e460 (sb_writers#26){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:377
 #1: ffff0000e87e6ae0 (&type->i_mutex_dir_key#19/1){+.+.}-{3:3}, at: do_renameat2+0x534/0x10c0 fs/namei.c:4924
 #2: ffff0000e87e7240 (&sb->s_type->i_mutex_key#32/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:824 [inline]
 #2: ffff0000e87e7240 (&sb->s_type->i_mutex_key#32/4){+.+.}-{3:3}, at: lock_two_nondirectories+0xc4/0x120 fs/inode.c:1124
 #3: ffff0000e87e6840 (&ni->ni_lock/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1105 [inline]
 #3: ffff0000e87e6840 (&ni->ni_lock/6){+.+.}-{3:3}, at: ntfs_rename+0x584/0xb10 fs/ntfs3/namei.c:314
 #4: ffff0000e87e6fa0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
 #4: ffff0000e87e6fa0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_rename+0x594/0xb10 fs/ntfs3/namei.c:315
 #5: ffff0000eb03c120 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_look_free_mft+0x190/0xd0c fs/ntfs3/fsntfs.c:542

stack backtrace:
CPU: 0 PID: 5857 Comm: syz.3.305 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
Call trace:
 dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 dump_stack+0x1c/0x58 lib/dump_stack.c:113
 __lock_acquire+0x62bc/0x7638 kernel/locking/lockdep.c:5012
 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623
 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596
 __mutex_lock kernel/locking/mutex.c:729 [inline]
 mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743
 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline]
 mi_read+0x26c/0x4d8 fs/ntfs3/record.c:148
 mi_format_new+0x174/0x514 fs/ntfs3/record.c:374
 ni_add_subrecord+0xd0/0x3c4 fs/ntfs3/frecord.c:372
 ntfs_look_free_mft+0x4c8/0xd0c fs/ntfs3/fsntfs.c:686
 ni_create_attr_list+0x764/0xf54 fs/ntfs3/frecord.c:850
 ni_ins_attr_ext+0x328/0x99c 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+0x544/0x818 fs/ntfs3/frecord.c:2985
 ni_rename+0xc8/0x1d8 fs/ntfs3/frecord.c:3025
 ntfs_rename+0x5c4/0xb10 fs/ntfs3/namei.c:318
 vfs_rename+0xac8/0xe04 fs/namei.c:4832
 do_renameat2+0xa00/0x10c0 fs/namei.c:4985
 __do_sys_renameat2 fs/namei.c:5018 [inline]
 __se_sys_renameat2 fs/namei.c:5015 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5015
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584