======================================================
WARNING: possible circular locking dependency detected
6.6.0-rc4-syzkaller-00298-g37faf07bf90a #0 Not tainted
------------------------------------------------------
kworker/u4:9/2810 is trying to acquire lock:
ffff888077b38940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline]
ffff888077b38940 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0x1d7f/0x3080 fs/ntfs/aops.c:436

but task is already holding lock:
ffff888077b3b310 (&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_truncate+0x263/0x2a50 fs/ntfs/inode.c:2383
       ntfs_truncate_vfs fs/ntfs/inode.c:2863 [inline]
       ntfs_setattr+0x3dd/0x5b0 fs/ntfs/inode.c:2915
       notify_change+0x742/0x11c0 fs/attr.c:499
       do_truncate+0x15c/0x220 fs/open.c:66
       do_sys_ftruncate+0x6a2/0x790 fs/open.c:194
       do_syscall_x64 arch/x86/entry/common.c:50 [inline]
       do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80
       entry_SYSCALL_64_after_hwframe+0x63/0xcd

-> #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_read_block fs/ntfs/aops.c:248 [inline]
       ntfs_read_folio+0x1d7f/0x3080 fs/ntfs/aops.c:436
       filemap_read_folio+0xe9/0x2c0 mm/filemap.c:2382
       do_read_cache_folio+0x205/0x540 mm/filemap.c:3742
       do_read_cache_page mm/filemap.c:3808 [inline]
       read_cache_page+0x5b/0x230 mm/filemap.c:3817
       read_mapping_page include/linux/pagemap.h:860 [inline]
       ntfs_map_page fs/ntfs/aops.h:75 [inline]
       ntfs_sync_mft_mirror+0x242/0x1eb0 fs/ntfs/mft.c:480
       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/u4:9/2810:
 #0: ffff888140050138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x787/0x15c0 kernel/workqueue.c:2605
 #1: ffffc9000a52fd80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7e9/0x15c0 kernel/workqueue.c:2606
 #2: ffff888077b3b310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4a/0x730 fs/ntfs/mft.c:154

stack backtrace:
CPU: 0 PID: 2810 Comm: kworker/u4:9 Not tainted 6.6.0-rc4-syzkaller-00298-g37faf07bf90a #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Workqueue: writeback wb_workfn (flush-7:0)
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_read_block fs/ntfs/aops.c:248 [inline]
 ntfs_read_folio+0x1d7f/0x3080 fs/ntfs/aops.c:436
 filemap_read_folio+0xe9/0x2c0 mm/filemap.c:2382
 do_read_cache_folio+0x205/0x540 mm/filemap.c:3742
 do_read_cache_page mm/filemap.c:3808 [inline]
 read_cache_page+0x5b/0x230 mm/filemap.c:3817
 read_mapping_page include/linux/pagemap.h:860 [inline]
 ntfs_map_page fs/ntfs/aops.h:75 [inline]
 ntfs_sync_mft_mirror+0x242/0x1eb0 fs/ntfs/mft.c:480
 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>