============================================
WARNING: possible recursive locking detected
6.7.0-rc4-syzkaller-00358-gf2e8a57ee903 #0 Not tainted
--------------------------------------------
syz-executor138/5065 is trying to acquire lock:
ffff888074349920 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
ffff888074349920 (&ni->ni_lock/4){+.+.}-{3:3}, at: mi_read+0x462/0x650 fs/ntfs3/record.c:148

but task is already holding lock:
ffff8880742a8860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
ffff8880742a8860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0x1b8/0x2a0 fs/ntfs3/namei.c:84

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

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

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by syz-executor138/5065:
 #0: ffff8880742a8b00 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:812 [inline]
 #0: ffff8880742a8b00 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: lookup_slow fs/namei.c:1710 [inline]
 #0: ffff8880742a8b00 (&type->i_mutex_dir_key#6){++++}-{3:3}, at: walk_component+0x33b/0x5a0 fs/namei.c:2002
 #1: ffff8880742a8860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
 #1: ffff8880742a8860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0x1b8/0x2a0 fs/ntfs3/namei.c:84

stack backtrace:
CPU: 1 PID: 5065 Comm: syz-executor138 Not tainted 6.7.0-rc4-syzkaller-00358-gf2e8a57ee903 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain kernel/locking/lockdep.c:3856 [inline]
 __lock_acquire+0x20f8/0x3b20 kernel/locking/lockdep.c:5137
 lock_acquire kernel/locking/lockdep.c:5754 [inline]
 lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x175/0x9d0 kernel/locking/mutex.c:747
 ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline]
 mi_read+0x462/0x650 fs/ntfs3/record.c:148
 ntfs_read_mft fs/ntfs3/inode.c:70 [inline]
 ntfs_iget5+0x4be/0x3810 fs/ntfs3/inode.c:534
 dir_search_u+0x162/0x3d0 fs/ntfs3/dir.c:264
 ntfs_lookup+0x1c5/0x2a0 fs/ntfs3/namei.c:85
 __lookup_slow+0x24d/0x450 fs/namei.c:1694
 lookup_slow fs/namei.c:1711 [inline]
 walk_component+0x349/0x5a0 fs/namei.c:2002
 lookup_last fs/namei.c:2459 [inline]
 path_lookupat+0x17f/0x770 fs/namei.c:2483
 filename_lookup+0x1e7/0x5b0 fs/namei.c:2512
 user_path_at_empty+0x42/0x60 fs/namei.c:2911
 user_path_at include/linux/namei.h:57 [inline]
 path_setxattr+0xa5/0x1d0 fs/xattr.c:667
 __do_sys_setxattr fs/xattr.c:688 [inline]
 __se_sys_setxattr fs/xattr.c:684 [inline]
 __x64_sys_setxattr+0xc4/0x160 fs/xattr.c:684
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7fdc157daa59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffec09368f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 0030656c69662f2e RCX: 00007fdc157daa59
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000180
RBP: 00007fdc1586c5f0 R08: 0000000000000000 R09: 00005555575114c0
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffec0936920
R13: 00007ffec0936b48 R14: 431bde82d7b634db R15: 00007fdc1582303b
 </TASK>