======================================================
WARNING: possible circular locking dependency detected
6.6.0-rc7-syzkaller-00012-ge017769f4ce2 #0 Not tainted
------------------------------------------------------
kworker/u16:2/53 is trying to acquire lock:
ffff888042524300 (&rl->lock){++++}-{3:3}, at: ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536

but task is already holding lock:
ffff888042526cd0 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&ni->mrec_lock){+.+.}-{3:3}:
       __mutex_lock_common kernel/locking/mutex.c:603 [inline]
       __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747
       map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154
       ntfs_attr_extend_allocation+0x268/0x3830 fs/ntfs/attrib.c:2002
       ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline]
       ntfs_file_write_iter+0xa98/0x1e00 fs/ntfs/file.c:1914
       call_write_iter include/linux/fs.h:1956 [inline]
       new_sync_write fs/read_write.c:491 [inline]
       vfs_write+0x650/0xe40 fs/read_write.c:584
       ksys_write+0x12f/0x250 fs/read_write.c:637
       do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]
       __do_fast_syscall_32+0x61/0xe0 arch/x86/entry/common.c:178
       do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203
       entry_SYSENTER_compat_after_hwframe+0x70/0x82

-> #0 (&rl->lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3134 [inline]
       check_prevs_add kernel/locking/lockdep.c:3253 [inline]
       validate_chain kernel/locking/lockdep.c:3868 [inline]
       __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136
       lock_acquire kernel/locking/lockdep.c:5753 [inline]
       lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718
       down_read+0x9c/0x470 kernel/locking/rwsem.c:1520
       ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536
       write_mft_record_nolock+0x1967/0x1d90 fs/ntfs/mft.c:787
       write_mft_record+0x14b/0x380 fs/ntfs/mft.h:95
       __ntfs_write_inode+0x91b/0xc30 fs/ntfs/inode.c:3051
       write_inode fs/fs-writeback.c:1456 [inline]
       __writeback_single_inode+0xa81/0xe70 fs/fs-writeback.c:1673
       writeback_sb_inodes+0x599/0x1070 fs/fs-writeback.c:1899
       wb_writeback+0x2a5/0xa90 fs/fs-writeback.c:2075
       wb_do_writeback fs/fs-writeback.c:2222 [inline]
       wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2262
       process_one_work+0x884/0x15c0 kernel/workqueue.c:2630
       process_scheduled_works kernel/workqueue.c:2703 [inline]
       worker_thread+0x8b9/0x1290 kernel/workqueue.c:2784
       kthread+0x33c/0x440 kernel/kthread.c:388
       ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
       ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304

other info that might help us debug this:

 Possible unsafe locking scenario:

       CPU0                    CPU1
       ----                    ----
  lock(&ni->mrec_lock);
                               lock(&rl->lock);
                               lock(&ni->mrec_lock);
  rlock(&rl->lock);

 *** DEADLOCK ***

3 locks held by kworker/u16:2/53:
 #0: ffff888015f50138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x787/0x15c0 kernel/workqueue.c:2605
 #1: ffffc9000073fd80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7e9/0x15c0 kernel/workqueue.c:2606
 #2: ffff888042526cd0
 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154

stack backtrace:
CPU: 1 PID: 53 Comm: kworker/u16:2 Not tainted 6.6.0-rc7-syzkaller-00012-ge017769f4ce2 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
Workqueue: writeback wb_workfn (flush-7:2)
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106
 check_noncircular+0x311/0x3f0 kernel/locking/lockdep.c:2187
 check_prev_add kernel/locking/lockdep.c:3134 [inline]
 check_prevs_add kernel/locking/lockdep.c:3253 [inline]
 validate_chain kernel/locking/lockdep.c:3868 [inline]
 __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136
 lock_acquire kernel/locking/lockdep.c:5753 [inline]
 lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718
 down_read+0x9c/0x470 kernel/locking/rwsem.c:1520
 ntfs_sync_mft_mirror+0x19bb/0x1eb0 fs/ntfs/mft.c:536
 write_mft_record_nolock+0x1967/0x1d90 fs/ntfs/mft.c:787
 write_mft_record+0x14b/0x380 fs/ntfs/mft.h:95
 __ntfs_write_inode+0x91b/0xc30 fs/ntfs/inode.c:3051
 write_inode fs/fs-writeback.c:1456 [inline]
 __writeback_single_inode+0xa81/0xe70 fs/fs-writeback.c:1673
 writeback_sb_inodes+0x599/0x1070 fs/fs-writeback.c:1899
 wb_writeback+0x2a5/0xa90 fs/fs-writeback.c:2075
 wb_do_writeback fs/fs-writeback.c:2222 [inline]
 wb_workfn+0x29c/0xfd0 fs/fs-writeback.c:2262
 process_one_work+0x884/0x15c0 kernel/workqueue.c:2630
 process_scheduled_works kernel/workqueue.c:2703 [inline]
 worker_thread+0x8b9/0x1290 kernel/workqueue.c:2784
 kthread+0x33c/0x440 kernel/kthread.c:388
 ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
 </TASK>