ntfs: (device loop9): ntfs_read_block(): Failed to read from inode 0xa, attribute type 0x80, vcn 0x0, offset 0x200 because its location on disk could not be determined even after retrying (error code -5). ntfs: (device loop9): ntfs_mapping_pairs_decompress(): Corrupt attribute. ntfs: volume version 3.1. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.9.475/7461 is trying to acquire lock: ffff0000e1b29a50 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x60/0x634 fs/ntfs/mft.c:154 but task is already holding lock: ffff0000e1b299c0 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x180/0x231c fs/ntfs/inode.c:2378 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&rl->lock){++++}-{3:3}: down_read+0x64/0x300 kernel/locking/rwsem.c:1520 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_read_folio+0xe7c/0x1cd4 fs/ntfs/aops.c:436 filemap_read_folio+0x134/0x384 mm/filemap.c:2490 do_read_cache_folio+0x24c/0x534 mm/filemap.c:3659 do_read_cache_page mm/filemap.c:3701 [inline] read_cache_page+0x6c/0x184 mm/filemap.c:3710 read_mapping_page include/linux/pagemap.h:793 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x1f4/0x18e4 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1048/0x1660 fs/ntfs/mft.c:787 write_mft_record+0x144/0x1b8 fs/ntfs/mft.h:95 __ntfs_write_inode+0x5c0/0xa60 fs/ntfs/inode.c:3050 ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2656 write_inode fs/fs-writeback.c:1521 [inline] __writeback_single_inode+0x5e0/0x157c fs/fs-writeback.c:1738 writeback_sb_inodes+0x870/0x1470 fs/fs-writeback.c:1964 __writeback_inodes_wb+0x104/0x370 fs/fs-writeback.c:2035 wb_writeback+0x420/0xfdc fs/fs-writeback.c:2140 wb_check_background_flush fs/fs-writeback.c:2206 [inline] wb_do_writeback fs/fs-writeback.c:2294 [inline] wb_workfn+0xb40/0xe18 fs/fs-writeback.c:2321 process_one_work+0x7e4/0x13bc kernel/workqueue.c:2292 worker_thread+0x8cc/0xfe8 kernel/workqueue.c:2439 kthread+0x254/0x2e0 kernel/kthread.c:376 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:850 -> #0 (&ni->mrec_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 __mutex_lock_common+0x1a0/0x1f3c 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/0x634 fs/ntfs/mft.c:154 ntfs_truncate+0x1e0/0x231c fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2862 [inline] ntfs_setattr+0x260/0x320 fs/ntfs/inode.c:2914 notify_change+0xb5c/0xe20 fs/attr.c:499 do_truncate+0x188/0x20c fs/open.c:65 vfs_truncate+0x23c/0x2b0 fs/open.c:111 do_sys_truncate+0xec/0x1b4 fs/open.c:134 __do_sys_truncate fs/open.c:146 [inline] __se_sys_truncate fs/open.c:144 [inline] __arm64_sys_truncate+0x5c/0x70 fs/open.c:144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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 *** 3 locks held by syz.9.475/7461: #0: ffff00010b248460 (sb_writers#28){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000e1b29d30 (&sb->s_type->i_mutex_key#39){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:764 [inline] #1: ffff0000e1b29d30 (&sb->s_type->i_mutex_key#39){+.+.}-{3:3}, at: do_truncate+0x174/0x20c fs/open.c:63 #2: ffff0000e1b299c0 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x180/0x231c fs/ntfs/inode.c:2378 stack backtrace: CPU: 0 PID: 7461 Comm: syz.9.475 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/14/2026 Call trace: dump_backtrace+0x1c4/0x1f0 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+0xf4/0x15c 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+0x264/0x2f8 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3095 [inline] check_prevs_add kernel/locking/lockdep.c:3214 [inline] validate_chain kernel/locking/lockdep.c:3830 [inline] __lock_acquire+0x2808/0x6634 kernel/locking/lockdep.c:5063 lock_acquire+0x20c/0x638 kernel/locking/lockdep.c:5676 __mutex_lock_common+0x1a0/0x1f3c 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/0x634 fs/ntfs/mft.c:154 ntfs_truncate+0x1e0/0x231c fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2862 [inline] ntfs_setattr+0x260/0x320 fs/ntfs/inode.c:2914 notify_change+0xb5c/0xe20 fs/attr.c:499 do_truncate+0x188/0x20c fs/open.c:65 vfs_truncate+0x23c/0x2b0 fs/open.c:111 do_sys_truncate+0xec/0x1b4 fs/open.c:134 __do_sys_truncate fs/open.c:146 [inline] __se_sys_truncate fs/open.c:144 [inline] __arm64_sys_truncate+0x5c/0x70 fs/open.c:144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x290 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x13c/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x5c/0x134 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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