============================================
WARNING: possible recursive locking detected
6.7.0-rc3-syzkaller-00033-g3b47bc037bd4 #0 Not tainted
--------------------------------------------
kworker/u4:7/2768 is trying to acquire lock:
ffff888034f1c360 (&ni->ni_lock#3){+.+.}-{3:3}, at: ntfs_set_state+0x1ff/0x6b0 fs/ntfs3/fsntfs.c:946

but task is already holding lock:
ffff8880382fbc00 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1144 [inline]
ffff8880382fbc00 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_write_inode+0x172/0x1090 fs/ntfs3/frecord.c:3262

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

       CPU0
       ----
  lock(&ni->ni_lock#3);
  lock(&ni->ni_lock#3);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

3 locks held by kworker/u4:7/2768:
 #0: ffff88801ae49d38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2605 [inline]
 #0: ffff88801ae49d38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2703
 #1: ffffc9000a9afd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2605 [inline]
 #1: ffffc9000a9afd20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2703
 #2: ffff8880382fbc00 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_trylock fs/ntfs3/ntfs_fs.h:1144 [inline]
 #2: ffff8880382fbc00 (&ni->ni_lock#3){+.+.}-{3:3}, at: ni_write_inode+0x172/0x1090 fs/ntfs3/frecord.c:3262

stack backtrace:
CPU: 0 PID: 2768 Comm: kworker/u4:7 Not tainted 6.7.0-rc3-syzkaller-00033-g3b47bc037bd4 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
Workqueue: writeback wb_workfn (flush-7:1)
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 check_deadlock kernel/locking/lockdep.c:3062 [inline]
 validate_chain+0x15dd/0x5ab0 kernel/locking/lockdep.c:3856
 __lock_acquire+0x1345/0x1fd0 kernel/locking/lockdep.c:5137
 lock_acquire+0x1e3/0x530 kernel/locking/lockdep.c:5754
 __mutex_lock_common kernel/locking/mutex.c:603 [inline]
 __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747
 ntfs_set_state+0x1ff/0x6b0 fs/ntfs3/fsntfs.c:946
 ntfs_iget5+0x3f0/0x3b70 fs/ntfs3/inode.c:537
 ni_update_parent+0x943/0xdc0 fs/ntfs3/frecord.c:3218
 ni_write_inode+0xe60/0x1090 fs/ntfs3/frecord.c:3321
 write_inode fs/fs-writeback.c:1473 [inline]
 __writeback_single_inode+0x69b/0xfc0 fs/fs-writeback.c:1690
 writeback_sb_inodes+0x8e3/0x1220 fs/fs-writeback.c:1916
 wb_writeback+0x44d/0xc70 fs/fs-writeback.c:2092
 wb_do_writeback fs/fs-writeback.c:2239 [inline]
 wb_workfn+0x400/0xfb0 fs/fs-writeback.c:2279
 process_one_work kernel/workqueue.c:2630 [inline]
 process_scheduled_works+0x90f/0x1420 kernel/workqueue.c:2703
 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2784
 kthread+0x2d3/0x370 kernel/kthread.c:388
 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:242
 </TASK>
ntfs3: loop1: Mark volume as dirty due to NTFS errors