====================================================== WARNING: possible circular locking dependency detected 6.1.135-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.1355/11336 is trying to acquire lock: ffff0000e1280190 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x60/0x5f4 fs/ntfs/mft.c:154 but task is already holding lock: ffff0000e1280100 (&rl->lock){++++}-{3:3}, at: ntfs_attr_extend_allocation+0x3ec/0x33e0 fs/ntfs/attrib.c:2001 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&rl->lock){++++}-{3:3}: down_read+0x64/0x304 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0xf18/0x1d40 fs/ntfs/aops.c:436 filemap_read_folio+0x130/0x37c mm/filemap.c:2490 do_read_cache_folio+0x24c/0x544 mm/filemap.c:3627 do_read_cache_page mm/filemap.c:3669 [inline] read_cache_page+0x6c/0x184 mm/filemap.c:3678 read_mapping_page include/linux/pagemap.h:791 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x1d0/0x187c fs/ntfs/mft.c:480 write_mft_record_nolock+0xff4/0x1604 fs/ntfs/mft.c:787 write_mft_record+0x144/0x1bc fs/ntfs/mft.h:95 __ntfs_write_inode+0x5b8/0xa68 fs/ntfs/inode.c:3050 ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1460 [inline] __writeback_single_inode+0x5e0/0x157c fs/fs-writeback.c:1677 writeback_sb_inodes+0x824/0x1404 fs/fs-writeback.c:1903 wb_writeback+0x400/0xfb0 fs/fs-writeback.c:2077 wb_do_writeback fs/fs-writeback.c:2220 [inline] wb_workfn+0x34c/0xd98 fs/fs-writeback.c:2260 process_one_work+0x7f4/0x13a8 kernel/workqueue.c:2292 worker_thread+0x8c8/0xfbc kernel/workqueue.c:2439 kthread+0x250/0x2d8 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864 -> #0 (&ni->mrec_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 __mutex_lock_common+0x190/0x1f38 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+0x60/0x5f4 fs/ntfs/mft.c:154 ntfs_attr_extend_allocation+0x3f4/0x33e0 fs/ntfs/attrib.c:2002 ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline] ntfs_file_write_iter+0x2c8/0x17e0 fs/ntfs/file.c:1915 call_write_iter include/linux/fs.h:2265 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x5ac/0x7c4 fs/read_write.c:584 ksys_write+0x120/0x210 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:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&rl->lock); lock(&ni->mrec_lock); lock(&rl->lock); lock(&ni->mrec_lock); *** DEADLOCK *** 4 locks held by syz.0.1355/11336: #0: ffff0000d1fcf9e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x114/0x16c fs/file.c:1040 #1: ffff0000df8c6460 (sb_writers#28){.+.+}-{0:0}, at: vfs_write+0x23c/0x7c4 fs/read_write.c:580 #2: ffff0000e1280470 (&sb->s_type->i_mutex_key#37){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #2: ffff0000e1280470 (&sb->s_type->i_mutex_key#37){+.+.}-{3:3}, at: ntfs_file_write_iter+0x78/0x17e0 fs/ntfs/file.c:1912 #3: ffff0000e1280100 (&rl->lock){++++}-{3:3}, at: ntfs_attr_extend_allocation+0x3ec/0x33e0 fs/ntfs/attrib.c:2001 stack backtrace: CPU: 1 PID: 11336 Comm: syz.0.1355 Not tainted 6.1.135-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __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:2048 check_noncircular+0x240/0x2d4 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x293c/0x6544 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662 __mutex_lock_common+0x190/0x1f38 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+0x60/0x5f4 fs/ntfs/mft.c:154 ntfs_attr_extend_allocation+0x3f4/0x33e0 fs/ntfs/attrib.c:2002 ntfs_prepare_file_for_write fs/ntfs/file.c:391 [inline] ntfs_file_write_iter+0x2c8/0x17e0 fs/ntfs/file.c:1915 call_write_iter include/linux/fs.h:2265 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x5ac/0x7c4 fs/read_write.c:584 ksys_write+0x120/0x210 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:38 [inline] invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 ntfs: (device loop0): ntfs_cluster_alloc(): Failed to allocate clusters, aborting (error -28).