======================================================
WARNING: possible circular locking dependency detected
6.6.0-rc7-syzkaller-g8de1e7afcc1c #0 Not tainted
------------------------------------------------------
kworker/u4:0/11 is trying to acquire lock:
ffff0000e2555bc0 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline]
ffff0000e2555bc0 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0xf70/0x1fd8 fs/ntfs/aops.c:436
but task is already holding lock:
ffff0000f3c79a50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x64/0x7b4 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+0x190/0x21a0 kernel/locking/mutex.c:603
__mutex_lock kernel/locking/mutex.c:747 [inline]
mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799
map_mft_record+0x64/0x7b4 fs/ntfs/mft.c:154
ntfs_attr_extend_allocation+0x458/0x3470 fs/ntfs/attrib.c:2002
ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline]
ntfs_file_write_iter+0x298/0x1738 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+0x628/0x93c fs/read_write.c:584
ksys_write+0x15c/0x26c fs/read_write.c:637
__do_sys_write fs/read_write.c:649 [inline]
__se_sys_write fs/read_write.c:646 [inline]
__arm64_sys_write+0x7c/0x90 fs/read_write.c:646
__invoke_syscall arch/arm64/kernel/syscall.c:37 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51
el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136
do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155
el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678
el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696
el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595
-> #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+0x3370/0x75e8 kernel/locking/lockdep.c:5136
lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5753
down_read+0x58/0x2fc kernel/locking/rwsem.c:1520
ntfs_read_block fs/ntfs/aops.c:248 [inline]
ntfs_read_folio+0xf70/0x1fd8 fs/ntfs/aops.c:436
filemap_read_folio+0x14c/0x39c mm/filemap.c:2382
do_read_cache_folio+0x114/0x548 mm/filemap.c:3742
do_read_cache_page+0x4c/0x260 mm/filemap.c:3808
read_cache_page+0x68/0x84 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+0x1cc/0x1890 fs/ntfs/mft.c:480
write_mft_record_nolock+0x100c/0x1630 fs/ntfs/mft.c:787
write_mft_record+0x144/0x1bc fs/ntfs/mft.h:95
__ntfs_write_inode+0x5cc/0xa78 fs/ntfs/inode.c:3051
ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2664
write_inode fs/fs-writeback.c:1456 [inline]
__writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1673
writeback_sb_inodes+0x718/0x1010 fs/fs-writeback.c:1899
wb_writeback+0x3f4/0xfc0 fs/fs-writeback.c:2075
wb_do_writeback fs/fs-writeback.c:2222 [inline]
wb_workfn+0x37c/0xf9c fs/fs-writeback.c:2262
process_one_work+0x694/0x1204 kernel/workqueue.c:2630
process_scheduled_works kernel/workqueue.c:2703 [inline]
worker_thread+0x938/0xef4 kernel/workqueue.c:2784
kthread+0x288/0x310 kernel/kthread.c:388
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857
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:0/11:
#0: ffff0000c18ccd38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x560/0x1204 kernel/workqueue.c:2603
#1: ffff800092d67c20 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x5a0/0x1204 kernel/workqueue.c:2605
#2: ffff0000f3c79a50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x64/0x7b4 fs/ntfs/mft.c:154
stack backtrace:
CPU: 0 PID: 11 Comm: kworker/u4:0 Not tainted 6.6.0-rc7-syzkaller-g8de1e7afcc1c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Workqueue: writeback wb_workfn (flush-7:0)
Call trace:
dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:233
show_stack+0x2c/0x44 arch/arm64/kernel/stacktrace.c:240
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106
dump_stack+0x1c/0x28 lib/dump_stack.c:113
print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2060
check_noncircular+0x310/0x404 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+0x3370/0x75e8 kernel/locking/lockdep.c:5136
lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5753
down_read+0x58/0x2fc kernel/locking/rwsem.c:1520
ntfs_read_block fs/ntfs/aops.c:248 [inline]
ntfs_read_folio+0xf70/0x1fd8 fs/ntfs/aops.c:436
filemap_read_folio+0x14c/0x39c mm/filemap.c:2382
do_read_cache_folio+0x114/0x548 mm/filemap.c:3742
do_read_cache_page+0x4c/0x260 mm/filemap.c:3808
read_cache_page+0x68/0x84 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+0x1cc/0x1890 fs/ntfs/mft.c:480
write_mft_record_nolock+0x100c/0x1630 fs/ntfs/mft.c:787
write_mft_record+0x144/0x1bc fs/ntfs/mft.h:95
__ntfs_write_inode+0x5cc/0xa78 fs/ntfs/inode.c:3051
ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2664
write_inode fs/fs-writeback.c:1456 [inline]
__writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1673
writeback_sb_inodes+0x718/0x1010 fs/fs-writeback.c:1899
wb_writeback+0x3f4/0xfc0 fs/fs-writeback.c:2075
wb_do_writeback fs/fs-writeback.c:2222 [inline]
wb_workfn+0x37c/0xf9c fs/fs-writeback.c:2262
process_one_work+0x694/0x1204 kernel/workqueue.c:2630
process_scheduled_works kernel/workqueue.c:2703 [inline]
worker_thread+0x938/0xef4 kernel/workqueue.c:2784
kthread+0x288/0x310 kernel/kthread.c:388
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857