======================================================
WARNING: possible circular locking dependency detected
6.1.42-syzkaller #0 Not tainted
------------------------------------------------------
kworker/u4:2/38 is trying to acquire lock:
ffff888073018940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline]
ffff888073018940 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436
but task is already holding lock:
ffff88807301b310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x48/0x630 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}:
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
__mutex_lock_common+0x1d4/0x2520 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:799
map_mft_record+0x48/0x630 fs/ntfs/mft.c:154
ntfs_truncate+0x263/0x2860 fs/ntfs/inode.c:2383
ntfs_truncate_vfs fs/ntfs/inode.c:2862 [inline]
ntfs_setattr+0x2c7/0x3a0 fs/ntfs/inode.c:2914
notify_change+0xdcd/0x1080 fs/attr.c:482
do_truncate+0x21c/0x300 fs/open.c:65
do_sys_ftruncate+0x2e2/0x380 fs/open.c:193
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/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:3098 [inline]
check_prevs_add kernel/locking/lockdep.c:3217 [inline]
validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
down_read+0x43/0x2e0 kernel/locking/rwsem.c:1520
ntfs_read_block fs/ntfs/aops.c:248 [inline]
ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436
filemap_read_folio+0x199/0x780 mm/filemap.c:2407
do_read_cache_folio+0x2ee/0x810 mm/filemap.c:3535
do_read_cache_page+0x32/0x220 mm/filemap.c:3577
read_mapping_page include/linux/pagemap.h:756 [inline]
ntfs_map_page fs/ntfs/aops.h:75 [inline]
ntfs_sync_mft_mirror+0x25b/0x1ad0 fs/ntfs/mft.c:480
write_mft_record_nolock+0x1151/0x18d0 fs/ntfs/mft.c:787
write_mft_record+0x149/0x310 fs/ntfs/mft.h:95
__ntfs_write_inode+0x6ff/0xbb0 fs/ntfs/inode.c:3050
write_inode fs/fs-writeback.c:1443 [inline]
__writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1655
writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1881
__writeback_inodes_wb+0x114/0x400 fs/fs-writeback.c:1952
wb_writeback+0x4b1/0xe10 fs/fs-writeback.c:2057
wb_check_background_flush fs/fs-writeback.c:2123 [inline]
wb_do_writeback fs/fs-writeback.c:2211 [inline]
wb_workfn+0xc9e/0x1020 fs/fs-writeback.c:2238
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
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 ***
4 locks held by kworker/u4:2/38:
#0: ffff888142ea3938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x77a/0x11f0
#1: ffffc90000af7d20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7bd/0x11f0 kernel/workqueue.c:2267
#2: ffff88807bfbc0e0 (&type->s_umount_key#63){.+.+}-{3:3}, at: trylock_super+0x1b/0xf0 fs/super.c:415
#3: ffff88807301b310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x48/0x630 fs/ntfs/mft.c:154
stack backtrace:
CPU: 0 PID: 38 Comm: kworker/u4:2 Not tainted 6.1.42-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2023
Workqueue: writeback wb_workfn (flush-7:0)
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
check_noncircular+0x2fa/0x3b0 kernel/locking/lockdep.c:2178
check_prev_add kernel/locking/lockdep.c:3098 [inline]
check_prevs_add kernel/locking/lockdep.c:3217 [inline]
validate_chain+0x1667/0x58e0 kernel/locking/lockdep.c:3832
__lock_acquire+0x125b/0x1f80 kernel/locking/lockdep.c:5056
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5669
down_read+0x43/0x2e0 kernel/locking/rwsem.c:1520
ntfs_read_block fs/ntfs/aops.c:248 [inline]
ntfs_read_folio+0x14c9/0x29d0 fs/ntfs/aops.c:436
filemap_read_folio+0x199/0x780 mm/filemap.c:2407
do_read_cache_folio+0x2ee/0x810 mm/filemap.c:3535
do_read_cache_page+0x32/0x220 mm/filemap.c:3577
read_mapping_page include/linux/pagemap.h:756 [inline]
ntfs_map_page fs/ntfs/aops.h:75 [inline]
ntfs_sync_mft_mirror+0x25b/0x1ad0 fs/ntfs/mft.c:480
write_mft_record_nolock+0x1151/0x18d0 fs/ntfs/mft.c:787
write_mft_record+0x149/0x310 fs/ntfs/mft.h:95
__ntfs_write_inode+0x6ff/0xbb0 fs/ntfs/inode.c:3050
write_inode fs/fs-writeback.c:1443 [inline]
__writeback_single_inode+0x67d/0x11e0 fs/fs-writeback.c:1655
writeback_sb_inodes+0xc21/0x1ac0 fs/fs-writeback.c:1881
__writeback_inodes_wb+0x114/0x400 fs/fs-writeback.c:1952
wb_writeback+0x4b1/0xe10 fs/fs-writeback.c:2057
wb_check_background_flush fs/fs-writeback.c:2123 [inline]
wb_do_writeback fs/fs-writeback.c:2211 [inline]
wb_workfn+0xc9e/0x1020 fs/fs-writeback.c:2238
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2292
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2439
kthread+0x26e/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</TASK>
__ntfs_error: 12 callbacks suppressed
ntfs: (device loop0): ntfs_write_block(): Writing beyond initialized size is not supported yet. Sorry.