====================================================== WARNING: possible circular locking dependency detected 6.7.0-rc8-syzkaller-g0802e17d9aca #0 Not tainted ------------------------------------------------------ syz-executor.1/29567 is trying to acquire lock: ffff0000da847510 (&ni->mrec_lock){+.+.}-{3:3}, at: map_mft_record+0x64/0x7b4 fs/ntfs/mft.c:154 but task is already holding lock: ffff0000da847480 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x170/0x2130 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+0x58/0x2fc kernel/locking/rwsem.c:1526 ntfs_read_block fs/ntfs/aops.c:242 [inline] ntfs_read_folio+0xd80/0x1c00 fs/ntfs/aops.c:430 filemap_read_folio+0x14c/0x39c mm/filemap.c:2323 do_read_cache_folio+0x114/0x548 mm/filemap.c:3700 do_read_cache_page mm/filemap.c:3766 [inline] read_cache_page+0x6c/0x15c mm/filemap.c:3775 read_mapping_page include/linux/pagemap.h:871 [inline] ntfs_map_page fs/ntfs/aops.h:75 [inline] ntfs_sync_mft_mirror+0x1cc/0x1890 fs/ntfs/mft.c:480 write_mft_record_nolock+0x100c/0x1630 fs/ntfs/mft.c:787 write_mft_record+0x144/0x1bc fs/ntfs/mft.h:95 __ntfs_write_inode+0x5cc/0xa78 fs/ntfs/inode.c:3052 ntfs_write_inode+0x68/0x90 fs/ntfs/super.c:2664 write_inode fs/fs-writeback.c:1473 [inline] __writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1690 writeback_sb_inodes+0x718/0x1010 fs/fs-writeback.c:1916 wb_writeback+0x3f4/0xfc0 fs/fs-writeback.c:2092 wb_do_writeback fs/fs-writeback.c:2239 [inline] wb_workfn+0x37c/0xf9c fs/fs-writeback.c:2279 process_one_work+0x694/0x1204 kernel/workqueue.c:2627 process_scheduled_works kernel/workqueue.c:2700 [inline] worker_thread+0x938/0xef4 kernel/workqueue.c:2781 kthread+0x288/0x310 kernel/kthread.c:388 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:857 -> #0 (&ni->mrec_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799 map_mft_record+0x64/0x7b4 fs/ntfs/mft.c:154 ntfs_truncate+0x1d0/0x2130 fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2864 [inline] ntfs_setattr+0x368/0x428 fs/ntfs/inode.c:2916 notify_change+0x9d4/0xc8c fs/attr.c:499 do_truncate+0x1c0/0x28c fs/open.c:66 do_sys_ftruncate+0x284/0x318 fs/open.c:194 __do_sys_ftruncate fs/open.c:205 [inline] __se_sys_ftruncate fs/open.c:203 [inline] __arm64_sys_ftruncate+0x60/0x74 fs/open.c:203 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 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-executor.1/29567: #0: ffff0000c45fc418 (sb_writers#29){.+.+}-{0:0}, at: do_sys_ftruncate+0x210/0x318 fs/open.c:191 #1: ffff0000da8477f0 (&sb->s_type->i_mutex_key#34){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline] #1: ffff0000da8477f0 (&sb->s_type->i_mutex_key#34){+.+.}-{3:3}, at: do_truncate+0x1ac/0x28c fs/open.c:64 #2: ffff0000da847480 (&rl->lock){++++}-{3:3}, at: ntfs_truncate+0x170/0x2130 fs/ntfs/inode.c:2378 stack backtrace: CPU: 1 PID: 29567 Comm: syz-executor.1 Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 dump_stack+0x1c/0x28 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2060 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x3384/0x763c kernel/locking/lockdep.c:5137 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5754 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x2c/0x38 kernel/locking/mutex.c:799 map_mft_record+0x64/0x7b4 fs/ntfs/mft.c:154 ntfs_truncate+0x1d0/0x2130 fs/ntfs/inode.c:2383 ntfs_truncate_vfs fs/ntfs/inode.c:2864 [inline] ntfs_setattr+0x368/0x428 fs/ntfs/inode.c:2916 notify_change+0x9d4/0xc8c fs/attr.c:499 do_truncate+0x1c0/0x28c fs/open.c:66 do_sys_ftruncate+0x284/0x318 fs/open.c:194 __do_sys_ftruncate fs/open.c:205 [inline] __se_sys_ftruncate fs/open.c:203 [inline] __arm64_sys_ftruncate+0x60/0x74 fs/open.c:203 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595