====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ kworker/u4:1/144 is trying to acquire lock: ffff88805f068940 (&rl->lock){++++}-{3:3}, at: ntfs_read_block fs/ntfs/aops.c:248 [inline] ffff88805f068940 (&rl->lock){++++}-{3:3}, at: ntfs_readpage+0x1294/0x2260 fs/ntfs/aops.c:435 but task is already holding lock: ffff88805f06b310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4e/0x620 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+0x1e3/0x2400 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743 map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154 ntfs_truncate+0x280/0x27c0 fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2862 [inline] ntfs_setattr+0x2bc/0x3a0 fs/ntfs/inode.c:2914 notify_change+0xbcd/0xee0 fs/attr.c:505 do_truncate+0x1ac/0x240 fs/open.c:65 vfs_truncate+0x262/0x2f0 fs/open.c:111 do_sys_truncate+0xf2/0x1c0 fs/open.c:134 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x66/0xd0 -> #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+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0x1294/0x2260 fs/ntfs/aops.c:435 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page+0x24/0x390 fs/ntfs/aops.h:75 ntfs_sync_mft_mirror+0x26c/0x1a20 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1242/0x1810 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x7cb/0xdc0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1505 [inline] __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715 writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940 wb_writeback+0x45d/0xbe0 fs/fs-writeback.c:2114 wb_do_writeback fs/fs-writeback.c:2257 [inline] wb_workfn+0x43a/0xf20 fs/fs-writeback.c:2298 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 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:1/144: #0: ffff888019fc8138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x761/0x1010 kernel/workqueue.c:-1 #1: ffffc9000173fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x79f/0x1010 kernel/workqueue.c:2285 #2: ffff88805f06b310 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x4e/0x620 fs/ntfs/mft.c:154 stack backtrace: CPU: 1 PID: 144 Comm: kworker/u4:1 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: writeback wb_workfn (flush-7:3) Call Trace: dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106 check_noncircular+0x296/0x330 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+0x2c42/0x7d10 kernel/locking/lockdep.c:5012 lock_acquire+0x19e/0x400 kernel/locking/lockdep.c:5623 down_read+0x44/0x2e0 kernel/locking/rwsem.c:1498 ntfs_read_block fs/ntfs/aops.c:248 [inline] ntfs_readpage+0x1294/0x2260 fs/ntfs/aops.c:435 do_read_cache_page+0x8a1/0x1030 mm/filemap.c:-1 read_mapping_page include/linux/pagemap.h:515 [inline] ntfs_map_page+0x24/0x390 fs/ntfs/aops.h:75 ntfs_sync_mft_mirror+0x26c/0x1a20 fs/ntfs/mft.c:480 write_mft_record_nolock+0x1242/0x1810 fs/ntfs/mft.c:787 write_mft_record fs/ntfs/mft.h:95 [inline] __ntfs_write_inode+0x7cb/0xdc0 fs/ntfs/inode.c:3050 write_inode fs/fs-writeback.c:1505 [inline] __writeback_single_inode+0x6c3/0xda0 fs/fs-writeback.c:1715 writeback_sb_inodes+0xa4e/0x1680 fs/fs-writeback.c:1940 wb_writeback+0x45d/0xbe0 fs/fs-writeback.c:2114 wb_do_writeback fs/fs-writeback.c:2257 [inline] wb_workfn+0x43a/0xf20 fs/fs-writeback.c:2298 process_one_work+0x85f/0x1010 kernel/workqueue.c:2310 worker_thread+0xaa6/0x1290 kernel/workqueue.c:2457 kthread+0x436/0x520 kernel/kthread.c:334 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287 IPv6: ADDRCONF(NETDEV_CHANGE): veth1_vlan: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_vlan: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vlan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): vlan1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): macvlan0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): macvlan1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_macvtap: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_macvtap: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): macvtap0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): macsec0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_0: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth0_to_batadv: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): batadv_slave_1: link becomes ready IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready