ntfs3(loop6): ino=3, ntfs_set_state failed, -22. ====================================================== WARNING: possible circular locking dependency detected 6.13.0-rc3-syzkaller-g573067a5a685 #0 Not tainted ------------------------------------------------------ syz.6.156/7452 is trying to acquire lock: ffff0000d8292b10 (&mm->mmap_lock){++++}-{4:4}, at: mmap_read_lock_killable+0x28/0x338 include/linux/mmap_lock.h:153 but task is already holding lock: ffff0000f1ecbe58 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:838 [inline] ffff0000f1ecbe58 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: ntfs_file_write_iter+0x210/0x630 fs/ntfs3/file.c:1240 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}: down_write+0x50/0xc0 kernel/locking/rwsem.c:1577 inode_lock include/linux/fs.h:818 [inline] ntfs_file_mmap+0x48c/0x6b8 fs/ntfs3/file.c:379 call_mmap include/linux/fs.h:2183 [inline] mmap_file mm/internal.h:124 [inline] __mmap_new_file_vma mm/vma.c:2291 [inline] __mmap_new_vma mm/vma.c:2355 [inline] __mmap_region+0x1854/0x2180 mm/vma.c:2456 mmap_region+0x1cc/0x370 mm/mmap.c:1348 do_mmap+0x8b0/0xfd0 mm/mmap.c:496 vm_mmap_pgoff+0x1a0/0x38c mm/util.c:580 ksys_mmap_pgoff+0x3a4/0x5c8 mm/mmap.c:542 __do_sys_mmap arch/arm64/kernel/sys.c:28 [inline] __se_sys_mmap arch/arm64/kernel/sys.c:21 [inline] __arm64_sys_mmap+0xf8/0x110 arch/arm64/kernel/sys.c:21 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&mm->mmap_lock){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 down_read_killable+0x64/0x338 kernel/locking/rwsem.c:1547 mmap_read_lock_killable+0x28/0x338 include/linux/mmap_lock.h:153 get_mmap_lock_carefully mm/memory.c:6158 [inline] lock_mm_and_find_vma+0x2a4/0x2d8 mm/memory.c:6209 do_page_fault+0x4dc/0x10a8 arch/arm64/mm/fault.c:668 do_translation_fault+0xc4/0x114 arch/arm64/mm/fault.c:783 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:919 el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:432 el1h_64_sync_handler+0x60/0xcc arch/arm64/kernel/entry-common.c:510 el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:595 __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:169 [inline] fault_in_readable+0x168/0x310 mm/gup.c:2237 fault_in_iov_iter_readable+0x1dc/0x22c lib/iov_iter.c:94 generic_perform_write+0x1f8/0x868 mm/filemap.c:4045 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4156 ntfs_file_write_iter+0x54c/0x630 fs/ntfs3/file.c:1267 new_sync_write fs/read_write.c:586 [inline] vfs_write+0x920/0xcf4 fs/read_write.c:679 ksys_write+0x15c/0x26c fs/read_write.c:731 __do_sys_write fs/read_write.c:742 [inline] __se_sys_write fs/read_write.c:739 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:739 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&sb->s_type->i_mutex_key#20); lock(&mm->mmap_lock); lock(&sb->s_type->i_mutex_key#20); rlock(&mm->mmap_lock); *** DEADLOCK *** 3 locks held by syz.6.156/7452: #0: ffff0000d1b44ef8 (&f->f_pos_lock){+.+.}-{4:4}, at: fdget_pos+0x220/0x2ac fs/file.c:1191 #1: ffff0000ea758420 (sb_writers#13){.+.+}-{0:0}, at: file_start_write include/linux/fs.h:2964 [inline] #1: ffff0000ea758420 (sb_writers#13){.+.+}-{0:0}, at: vfs_write+0x354/0xcf4 fs/read_write.c:675 #2: ffff0000f1ecbe58 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: inode_trylock include/linux/fs.h:838 [inline] #2: ffff0000f1ecbe58 (&sb->s_type->i_mutex_key#20){+.+.}-{4:4}, at: ntfs_file_write_iter+0x210/0x630 fs/ntfs3/file.c:1240 stack backtrace: CPU: 1 UID: 0 PID: 7452 Comm: syz.6.156 Not tainted 6.13.0-rc3-syzkaller-g573067a5a685 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xe4/0x150 lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x154/0x1c0 kernel/locking/lockdep.c:2074 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2206 check_prev_add kernel/locking/lockdep.c:3161 [inline] check_prevs_add kernel/locking/lockdep.c:3280 [inline] validate_chain kernel/locking/lockdep.c:3904 [inline] __lock_acquire+0x34f0/0x7904 kernel/locking/lockdep.c:5226 lock_acquire+0x23c/0x724 kernel/locking/lockdep.c:5849 down_read_killable+0x64/0x338 kernel/locking/rwsem.c:1547 mmap_read_lock_killable+0x28/0x338 include/linux/mmap_lock.h:153 get_mmap_lock_carefully mm/memory.c:6158 [inline] lock_mm_and_find_vma+0x2a4/0x2d8 mm/memory.c:6209 do_page_fault+0x4dc/0x10a8 arch/arm64/mm/fault.c:668 do_translation_fault+0xc4/0x114 arch/arm64/mm/fault.c:783 do_mem_abort+0x74/0x200 arch/arm64/mm/fault.c:919 el1_abort+0x3c/0x5c arch/arm64/kernel/entry-common.c:432 el1h_64_sync_handler+0x60/0xcc arch/arm64/kernel/entry-common.c:510 el1h_64_sync+0x6c/0x70 arch/arm64/kernel/entry.S:595 __uaccess_mask_ptr arch/arm64/include/asm/uaccess.h:169 [inline] (P) fault_in_readable+0x168/0x310 mm/gup.c:2237 (P) fault_in_iov_iter_readable+0x1dc/0x22c lib/iov_iter.c:94 generic_perform_write+0x1f8/0x868 mm/filemap.c:4045 __generic_file_write_iter+0xfc/0x204 mm/filemap.c:4156 ntfs_file_write_iter+0x54c/0x630 fs/ntfs3/file.c:1267 new_sync_write fs/read_write.c:586 [inline] vfs_write+0x920/0xcf4 fs/read_write.c:679 ksys_write+0x15c/0x26c fs/read_write.c:731 __do_sys_write fs/read_write.c:742 [inline] __se_sys_write fs/read_write.c:739 [inline] __arm64_sys_write+0x7c/0x90 fs/read_write.c:739 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x168 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x84/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 ntfs3(loop6): ino=3, ntfs_set_state failed, -22. ntfs3(loop6): Mark volume as dirty due to NTFS errors ntfs3(loop6): ino=3, ntfs_set_state failed, -22.