====================================================== WARNING: possible circular locking dependency detected 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0 Not tainted ------------------------------------------------------ kworker/u4:0/9 is trying to acquire lock: ffff0000cabac6c0 (&rl->lock){++++}-{3:3}, at: ntfs_read_block+0x2d0/0x1110 fs/ntfs/aops.c:248 but task is already holding lock: ffff0000e0939110 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x40/0xfc 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+0xd4/0xca8 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 map_mft_record+0x40/0xfc fs/ntfs/mft.c:154 ntfs_attr_extend_allocation+0x224/0x1838 fs/ntfs/attrib.c:2002 ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline] ntfs_file_write_iter+0x160/0x4f0 fs/ntfs/file.c:1915 call_write_iter include/linux/fs.h:2199 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x2dc/0x46c fs/read_write.c:584 ksys_write+0xb4/0x160 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+0x24/0x34 fs/read_write.c:646 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall arch/arm64/kernel/syscall.c:52 [inline] el0_svc_common+0x138/0x220 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x48/0x140 arch/arm64/kernel/syscall.c:197 el0_svc+0x58/0x150 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:584 -> #0 (&rl->lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055 lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668 down_read+0x5c/0x78 kernel/locking/rwsem.c:1509 ntfs_read_block+0x2d0/0x1110 fs/ntfs/aops.c:248 ntfs_read_folio+0x594/0x758 fs/ntfs/aops.c:436 filemap_read_folio+0xc4/0x468 mm/filemap.c:2407 do_read_cache_folio+0x1c8/0x588 mm/filemap.c:3534 do_read_cache_page mm/filemap.c:3576 [inline] read_cache_page+0x40/0x174 mm/filemap.c:3585 read_mapping_page include/linux/pagemap.h:756 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0xb4/0x109c fs/ntfs/mft.c:480 write_mft_record_nolock+0x814/0xc70 fs/ntfs/mft.c:787 write_mft_record+0xe4/0x230 fs/ntfs/mft.h:95 __ntfs_write_inode+0x32c/0x554 fs/ntfs/inode.c:3050 ntfs_write_inode+0x3c/0x4c fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1440 [inline] __writeback_single_inode+0x240/0x2e4 fs/fs-writeback.c:1652 writeback_sb_inodes+0x3e4/0x85c fs/fs-writeback.c:1878 wb_writeback+0x198/0x328 fs/fs-writeback.c:2052 wb_do_writeback+0xc8/0x384 fs/fs-writeback.c:2195 wb_workfn+0x70/0x15c fs/fs-writeback.c:2235 process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 worker_thread+0x340/0x610 kernel/workqueue.c:2436 kthread+0x12c/0x158 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863 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:0/9: #0: ffff0000c0df8538 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x270/0x504 kernel/workqueue.c:2262 #1: ffff80000f2a3d80 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x29c/0x504 kernel/workqueue.c:2264 #2: ffff0000e0939110 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x40/0xfc fs/ntfs/mft.c:154 stack backtrace: CPU: 0 PID: 9 Comm: kworker/u4:0 Not tainted 6.1.0-rc8-syzkaller-33330-ga5541c0811a0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: writeback wb_workfn (flush-7:1) Call trace: dump_backtrace+0x1c4/0x1f0 arch/arm64/kernel/stacktrace.c:156 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:163 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x104/0x16c lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x2c4/0x2c8 kernel/locking/lockdep.c:2055 check_noncircular+0x14c/0x154 kernel/locking/lockdep.c:2177 check_prev_add kernel/locking/lockdep.c:3097 [inline] check_prevs_add kernel/locking/lockdep.c:3216 [inline] validate_chain kernel/locking/lockdep.c:3831 [inline] __lock_acquire+0x1530/0x3084 kernel/locking/lockdep.c:5055 lock_acquire+0x100/0x1f8 kernel/locking/lockdep.c:5668 down_read+0x5c/0x78 kernel/locking/rwsem.c:1509 ntfs_read_block+0x2d0/0x1110 fs/ntfs/aops.c:248 ntfs_read_folio+0x594/0x758 fs/ntfs/aops.c:436 filemap_read_folio+0xc4/0x468 mm/filemap.c:2407 do_read_cache_folio+0x1c8/0x588 mm/filemap.c:3534 do_read_cache_page mm/filemap.c:3576 [inline] read_cache_page+0x40/0x174 mm/filemap.c:3585 read_mapping_page include/linux/pagemap.h:756 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0xb4/0x109c fs/ntfs/mft.c:480 write_mft_record_nolock+0x814/0xc70 fs/ntfs/mft.c:787 write_mft_record+0xe4/0x230 fs/ntfs/mft.h:95 __ntfs_write_inode+0x32c/0x554 fs/ntfs/inode.c:3050 ntfs_write_inode+0x3c/0x4c fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1440 [inline] __writeback_single_inode+0x240/0x2e4 fs/fs-writeback.c:1652 writeback_sb_inodes+0x3e4/0x85c fs/fs-writeback.c:1878 wb_writeback+0x198/0x328 fs/fs-writeback.c:2052 wb_do_writeback+0xc8/0x384 fs/fs-writeback.c:2195 wb_workfn+0x70/0x15c fs/fs-writeback.c:2235 process_one_work+0x2d8/0x504 kernel/workqueue.c:2289 worker_thread+0x340/0x610 kernel/workqueue.c:2436 kthread+0x12c/0x158 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:863