======================================================
WARNING: possible circular locking dependency detected
syzkaller #0 Not tainted
------------------------------------------------------
kworker/u4:5/4338 is trying to acquire lock:
ffff88805a820940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline]
ffff88805a820940 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0x1463/0x29c0 fs/ntfs/aops.c:436

but task is already holding lock:
ffff88805a823310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4c/0x650 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+0x12d/0xaf0 kernel/locking/mutex.c:747
       map_mft_record+0x4c/0x650 fs/ntfs/mft.c:154
       ntfs_truncate+0x280/0x27c0 fs/ntfs/inode.c:2383
       ntfs_truncate_vfs fs/ntfs/inode.c:2862 [inline]
       ntfs_setattr+0x2bc/0x3a0 fs/ntfs/inode.c:2914
       notify_change+0xc74/0xf40 fs/attr.c:499
       do_truncate+0x1ac/0x240 fs/open.c:65
       vfs_truncate+0x262/0x2f0 fs/open.c:111
       do_sys_truncate+0xf2/0x1c0 fs/open.c:134
       do_syscall_x64 arch/x86/entry/common.c:46 [inline]
       do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
       entry_SYSCALL_64_after_hwframe+0x68/0xd2

-> #0 (&rl->lock){++++}-{3:3}:
       check_prev_add kernel/locking/lockdep.c:3090 [inline]
       check_prevs_add kernel/locking/lockdep.c:3209 [inline]
       validate_chain kernel/locking/lockdep.c:3825 [inline]
       __lock_acquire+0x2d07/0x7d10 kernel/locking/lockdep.c:5049
       lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662
       down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
       ntfs_read_block fs/ntfs/aops.c:248 [inline]
       ntfs_read_folio+0x1463/0x29c0 fs/ntfs/aops.c:436
       filemap_read_folio+0x16b/0x770 mm/filemap.c:2490
       do_read_cache_folio+0x2a0/0x760 mm/filemap.c:3659
       do_read_cache_page+0x32/0x220 mm/filemap.c:3701
       read_mapping_page include/linux/pagemap.h:793 [inline]
       ntfs_map_page fs/ntfs/aops.h:75 [inline]
       ntfs_sync_mft_mirror+0x24f/0x1ad0 fs/ntfs/mft.c:480
       write_mft_record_nolock+0x1188/0x1900 fs/ntfs/mft.c:787
       write_mft_record+0x136/0x300 fs/ntfs/mft.h:95
       __ntfs_write_inode+0x724/0xbf0 fs/ntfs/inode.c:3050
       write_inode fs/fs-writeback.c:1470 [inline]
       __writeback_single_inode+0x75b/0x1160 fs/fs-writeback.c:1687
       writeback_sb_inodes+0xb30/0x1850 fs/fs-writeback.c:1913
       wb_writeback+0x482/0xd50 fs/fs-writeback.c:2087
       wb_do_writeback fs/fs-writeback.c:2230 [inline]
       wb_workfn+0x423/0xee0 fs/fs-writeback.c:2270
       process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
       worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
       kthread+0x29d/0x330 kernel/kthread.c:376
       ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295

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);
  lock(&rl->lock);

 *** DEADLOCK ***

3 locks held by kworker/u4:5/4338:
 #0: ffff88801c26e938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #1: ffffc90004587d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
 #2: ffff88805a823310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4c/0x650 fs/ntfs/mft.c:154

stack backtrace:
CPU: 1 PID: 4338 Comm: kworker/u4:5 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: writeback wb_workfn (flush-7:3)
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
 check_noncircular+0x296/0x330 kernel/locking/lockdep.c:2170
 check_prev_add kernel/locking/lockdep.c:3090 [inline]
 check_prevs_add kernel/locking/lockdep.c:3209 [inline]
 validate_chain kernel/locking/lockdep.c:3825 [inline]
 __lock_acquire+0x2d07/0x7d10 kernel/locking/lockdep.c:5049
 lock_acquire+0x1bb/0x4a0 kernel/locking/lockdep.c:5662
 down_read+0x42/0x2d0 kernel/locking/rwsem.c:1520
 ntfs_read_block fs/ntfs/aops.c:248 [inline]
 ntfs_read_folio+0x1463/0x29c0 fs/ntfs/aops.c:436
 filemap_read_folio+0x16b/0x770 mm/filemap.c:2490
 do_read_cache_folio+0x2a0/0x760 mm/filemap.c:3659
 do_read_cache_page+0x32/0x220 mm/filemap.c:3701
 read_mapping_page include/linux/pagemap.h:793 [inline]
 ntfs_map_page fs/ntfs/aops.h:75 [inline]
 ntfs_sync_mft_mirror+0x24f/0x1ad0 fs/ntfs/mft.c:480
 write_mft_record_nolock+0x1188/0x1900 fs/ntfs/mft.c:787
 write_mft_record+0x136/0x300 fs/ntfs/mft.h:95
 __ntfs_write_inode+0x724/0xbf0 fs/ntfs/inode.c:3050
 write_inode fs/fs-writeback.c:1470 [inline]
 __writeback_single_inode+0x75b/0x1160 fs/fs-writeback.c:1687
 writeback_sb_inodes+0xb30/0x1850 fs/fs-writeback.c:1913
 wb_writeback+0x482/0xd50 fs/fs-writeback.c:2087
 wb_do_writeback fs/fs-writeback.c:2230 [inline]
 wb_workfn+0x423/0xee0 fs/fs-writeback.c:2270
 process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
 worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
 kthread+0x29d/0x330 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
 </TASK>
ntfs: (device loop3): ntfs_write_block(): Writing beyond initialized size is not supported yet. Sorry.