====================================================== WARNING: possible circular locking dependency detected 5.15.181-syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:4/337 is trying to acquire lock: ffff0000deb50940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline] ffff0000deb50940 (&rl->lock){++++}-{3:3}, at: ntfs_readpage+0xee8/0x1d94 fs/ntfs/aops.c:435 but task is already holding lock: ffff0000deb53310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x68/0x740 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+0x194/0x1edc kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xac/0x11c kernel/locking/mutex.c:743 map_mft_record+0x68/0x740 fs/ntfs/mft.c:154 ntfs_attr_extend_allocation+0x3f4/0x33c8 fs/ntfs/attrib.c:2002 ntfs_prepare_file_for_write fs/ntfs/file.c:395 [inline] ntfs_file_write_iter+0x388/0x1738 fs/ntfs/file.c:1919 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x7c8/0xa2c fs/read_write.c:594 ksys_write+0x120/0x210 fs/read_write.c:647 __do_sys_write fs/read_write.c:659 [inline] __se_sys_write fs/read_write.c:656 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:656 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x78/0x1e0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0xcc/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #0 (&rl->lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 down_read+0xc0/0x390 kernel/locking/rwsem.c:1498 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0xee8/0x1d94 fs/ntfs/aops.c:435 do_read_cache_page+0x5f4/0x8f8 mm/filemap.c:-1 read_cache_page+0x68/0x88 mm/filemap.c:3574 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x1d4/0x16e4 fs/ntfs/mft.c:480 write_mft_record_nolock+0x105c/0x16fc fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x6c8/0xd50 fs/ntfs/inode.c:3050 ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1495 [inline] __writeback_single_inode+0x560/0x11f0 fs/fs-writeback.c:1705 writeback_sb_inodes+0x7fc/0x1378 fs/fs-writeback.c:1930 __writeback_inodes_wb+0x110/0x394 fs/fs-writeback.c:2001 wb_writeback+0x3ec/0xe44 fs/fs-writeback.c:2106 wb_check_background_flush fs/fs-writeback.c:2172 [inline] wb_do_writeback fs/fs-writeback.c:2260 [inline] wb_workfn+0xa7c/0xdd8 fs/fs-writeback.c:2288 process_one_work+0x79c/0x1140 kernel/workqueue.c:2310 worker_thread+0x8f4/0x101c kernel/workqueue.c:2457 kthread+0x374/0x454 kernel/kthread.c:334 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870 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:4/337: #0: ffff0000c21d8138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x678/0x1140 kernel/workqueue.c:2283 #1: ffff80001bf07c00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x6b8/0x1140 kernel/workqueue.c:2285 #2: ffff0000ccbbe0e0 (&type->s_umount_key#62){.+.+}-{3:3}, at: trylock_super+0x24/0xf4 fs/super.c:418 #3: ffff0000deb53310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x68/0x740 fs/ntfs/mft.c:154 stack backtrace: CPU: 1 PID: 337 Comm: kworker/u4:4 Not tainted 5.15.181-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025 Workqueue: writeback wb_workfn (flush-7:2) Call trace: dump_backtrace+0x0/0x43c arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf8/0x160 lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2011 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x2928/0x651c kernel/locking/lockdep.c:5012 lock_acquire+0x1f4/0x620 kernel/locking/lockdep.c:5623 down_read+0xc0/0x390 kernel/locking/rwsem.c:1498 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0xee8/0x1d94 fs/ntfs/aops.c:435 do_read_cache_page+0x5f4/0x8f8 mm/filemap.c:-1 read_cache_page+0x68/0x88 mm/filemap.c:3574 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x1d4/0x16e4 fs/ntfs/mft.c:480 write_mft_record_nolock+0x105c/0x16fc fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x6c8/0xd50 fs/ntfs/inode.c:3050 ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1495 [inline] __writeback_single_inode+0x560/0x11f0 fs/fs-writeback.c:1705 writeback_sb_inodes+0x7fc/0x1378 fs/fs-writeback.c:1930 __writeback_inodes_wb+0x110/0x394 fs/fs-writeback.c:2001 wb_writeback+0x3ec/0xe44 fs/fs-writeback.c:2106 wb_check_background_flush fs/fs-writeback.c:2172 [inline] wb_do_writeback fs/fs-writeback.c:2260 [inline] wb_workfn+0xa7c/0xdd8 fs/fs-writeback.c:2288 process_one_work+0x79c/0x1140 kernel/workqueue.c:2310 worker_thread+0x8f4/0x101c kernel/workqueue.c:2457 kthread+0x374/0x454 kernel/kthread.c:334 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870