============================================
WARNING: possible recursive locking detected
syzkaller #0 Not tainted
--------------------------------------------
syz.3.56/4573 is trying to acquire lock:
ffff888071a19e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ffff888071a19e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: mi_read+0x2d0/0x590 fs/ntfs3/record.c:148

but task is already holding lock:
ffff888071ab25e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
ffff888071ab25e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_link+0xf2/0x280 fs/ntfs3/namei.c:149

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.56/4573:
 #0: ffff888054386460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:402
 #1: ffff888071ab2120 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #1: ffff888071ab2120 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: filename_create+0x1f2/0x450 fs/namei.c:3884
 #2: ffff888071ab2880 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #2: ffff888071ab2880 (&sb->s_type->i_mutex_key#25){+.+.}-{3:3}, at: vfs_link+0x513/0x7c0 fs/namei.c:4598
 #3: ffff888071ab1e80 (&ni->ni_lock/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1107 [inline]
 #3: ffff888071ab1e80 (&ni->ni_lock/6){+.+.}-{3:3}, at: ntfs_link+0xd7/0x280 fs/ntfs3/namei.c:147
 #4: ffff888071ab25e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
 #4: ffff888071ab25e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_link+0xf2/0x280 fs/ntfs3/namei.c:149
 #5: ffff88805437c120 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_look_free_mft+0x160/0xd40 fs/ntfs3/fsntfs.c:542

stack backtrace:
CPU: 0 PID: 4573 Comm: syz.3.56 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
 __lock_acquire+0x122f/0x7c50 kernel/locking/lockdep.c:-1
 lock_acquire+0x1b4/0x490 kernel/locking/lockdep.c:5662
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x120/0xaf0 kernel/locking/mutex.c:747
 ni_lock fs/ntfs3/ntfs_fs.h:1102 [inline]
 mi_read+0x2d0/0x590 fs/ntfs3/record.c:148
 mi_format_new+0x1ba/0x5d0 fs/ntfs3/record.c:414
 ni_add_subrecord+0xcc/0x440 fs/ntfs3/frecord.c:373
 ntfs_look_free_mft+0x6a4/0xd40 fs/ntfs3/fsntfs.c:686
 ni_create_attr_list+0x8a2/0x12c0 fs/ntfs3/frecord.c:875
 ni_ins_attr_ext+0x31a/0xa00 fs/ntfs3/frecord.c:976
 ni_insert_attr fs/ntfs3/frecord.c:1143 [inline]
 ni_insert_resident fs/ntfs3/frecord.c:1527 [inline]
 ni_add_name+0x4fb/0xa00 fs/ntfs3/frecord.c:3105
 ntfs_link_inode+0x12e/0x170 fs/ntfs3/inode.c:1711
 ntfs_link+0x114/0x280 fs/ntfs3/namei.c:154
 vfs_link+0x615/0x7c0 fs/namei.c:4607
 do_linkat+0x274/0x550 fs/namei.c:4678
 __do_sys_link fs/namei.c:4712 [inline]
 __se_sys_link fs/namei.c:4710 [inline]
 __x64_sys_link+0x82/0x90 fs/namei.c:4710
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fa96f98efc9
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:00007fa97074c038 EFLAGS: 00000246 ORIG_RAX: 0000000000000056
RAX: ffffffffffffffda RBX: 00007fa96fbe6180 RCX: 00007fa96f98efc9
RDX: 0000000000000000 RSI: 0000200000000640 RDI: 0000200000000940
RBP: 00007fa96fa11f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fa96fbe6218 R14: 00007fa96fbe6180 R15: 00007ffcd68d4ac8
 </TASK>