====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:14/3483 is trying to acquire lock: ffff888058660940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline] ffff888058660940 (&rl->lock){++++}-{3:3}, at: ntfs_read_folio+0x1433/0x2960 fs/ntfs/aops.c:436 but task is already holding lock: ffff888058663310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x50/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+0x135/0xc80 kernel/locking/mutex.c:747 map_mft_record+0x50/0x650 fs/ntfs/mft.c:154 ntfs_truncate+0x284/0x2800 fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2863 [inline] ntfs_setattr+0x341/0x420 fs/ntfs/inode.c:2915 notify_change+0xb05/0xde0 fs/attr.c:499 do_truncate+0x1b0/0x240 fs/open.c:66 handle_truncate fs/namei.c:3342 [inline] do_open fs/namei.c:3687 [inline] path_openat+0x2a7e/0x3270 fs/namei.c:3844 do_filp_open+0x1f2/0x430 fs/namei.c:3871 do_sys_openat2+0x134/0x1d0 fs/open.c:1422 do_sys_open fs/open.c:1437 [inline] __do_sys_openat fs/open.c:1453 [inline] __se_sys_openat fs/open.c:1448 [inline] __x64_sys_openat+0x139/0x160 fs/open.c:1448 do_syscall_x64 arch/x86/entry/common.c:46 [inline] do_syscall_64+0x55/0xb0 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:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5756 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0x1433/0x2960 fs/ntfs/aops.c:436 filemap_read_folio+0x16b/0x790 mm/filemap.c:2420 do_read_cache_folio+0x485/0x7f0 mm/filemap.c:3809 do_read_cache_page+0x32/0x260 mm/filemap.c:3875 read_mapping_page include/linux/pagemap.h:892 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x252/0x1a80 fs/ntfs/mft.c:480 write_mft_record_nolock+0x120b/0x1990 fs/ntfs/mft.c:787 write_mft_record+0x136/0x300 fs/ntfs/mft.h:95 __ntfs_write_inode+0x6bb/0xbf0 fs/ntfs/inode.c:3051 write_inode fs/fs-writeback.c:1534 [inline] __writeback_single_inode+0x720/0xee0 fs/fs-writeback.c:1751 writeback_sb_inodes+0x813/0x1020 fs/fs-writeback.c:1977 wb_writeback+0x45e/0xbe0 fs/fs-writeback.c:2156 wb_do_writeback fs/fs-writeback.c:2303 [inline] wb_workfn+0x400/0xe60 fs/fs-writeback.c:2343 process_one_work kernel/workqueue.c:2657 [inline] process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2734 worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2815 kthread+0x2fa/0x390 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293 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:14/3483: #0: ffff88801d26cd38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2632 [inline] #0: ffff88801d26cd38 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2734 #1: ffffc9000cbb7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2632 [inline] #1: ffffc9000cbb7d00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x975/0x1600 kernel/workqueue.c:2734 #2: ffff888058663310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x50/0x650 fs/ntfs/mft.c:154 stack backtrace: CPU: 0 PID: 3483 Comm: kworker/u4:14 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026 Workqueue: writeback wb_workfn (flush-7:0) Call Trace: dump_stack_lvl+0x18c/0x250 lib/dump_stack.c:106 check_noncircular+0x2fc/0x400 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:3869 [inline] __lock_acquire+0x37ef/0x7d80 kernel/locking/lockdep.c:5137 lock_acquire+0x19e/0x420 kernel/locking/lockdep.c:5756 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0x1433/0x2960 fs/ntfs/aops.c:436 filemap_read_folio+0x16b/0x790 mm/filemap.c:2420 do_read_cache_folio+0x485/0x7f0 mm/filemap.c:3809 do_read_cache_page+0x32/0x260 mm/filemap.c:3875 read_mapping_page include/linux/pagemap.h:892 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x252/0x1a80 fs/ntfs/mft.c:480 write_mft_record_nolock+0x120b/0x1990 fs/ntfs/mft.c:787 write_mft_record+0x136/0x300 fs/ntfs/mft.h:95 __ntfs_write_inode+0x6bb/0xbf0 fs/ntfs/inode.c:3051 write_inode fs/fs-writeback.c:1534 [inline] __writeback_single_inode+0x720/0xee0 fs/fs-writeback.c:1751 writeback_sb_inodes+0x813/0x1020 fs/fs-writeback.c:1977 wb_writeback+0x45e/0xbe0 fs/fs-writeback.c:2156 wb_do_writeback fs/fs-writeback.c:2303 [inline] wb_workfn+0x400/0xe60 fs/fs-writeback.c:2343 process_one_work kernel/workqueue.c:2657 [inline] process_scheduled_works+0xa60/0x1600 kernel/workqueue.c:2734 worker_thread+0xa5e/0xfe0 kernel/workqueue.c:2815 kthread+0x2fa/0x390 kernel/kthread.c:388 ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152 ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293