====================================================== WARNING: possible circular locking dependency detected 6.5.0-rc7-syzkaller-gfe4469582053 #0 Not tainted ------------------------------------------------------ syz-executor.3/23668 is trying to acquire lock: ffff000135d70860 (&ni->ni_lock#3){+.+.}-{3:3}, at: ntfs_set_state+0x1a4/0x608 fs/ntfs3/fsntfs.c:946 but task is already holding lock: ffff000135d72d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] ffff000135d72d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf8/0x1f8 fs/ntfs3/namei.c:84 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->ni_lock/4){+.+.}-{3:3}: __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 ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] mi_read+0x26c/0x4d8 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:69 [inline] ntfs_iget5+0x360/0x2bac fs/ntfs3/inode.c:530 ni_update_parent+0x688/0xa58 fs/ntfs3/frecord.c:3212 ni_write_inode+0x84c/0xda8 fs/ntfs3/frecord.c:3311 ntfs3_write_inode+0x70/0x98 fs/ntfs3/inode.c:1024 write_inode fs/fs-writeback.c:1456 [inline] __writeback_single_inode+0x5a8/0x146c fs/fs-writeback.c:1668 writeback_single_inode+0x1c0/0x64c fs/fs-writeback.c:1724 write_inode_now+0x198/0x230 fs/fs-writeback.c:2766 ntfs_extend+0x2fc/0x3f4 fs/ntfs3/file.c:355 ntfs_file_write_iter+0x2a0/0x580 fs/ntfs3/file.c:1076 call_write_iter include/linux/fs.h:1877 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x628/0x93c fs/read_write.c:584 ksys_write+0x15c/0x26c 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: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+0x58/0x16c 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:591 -> #0 (&ni->ni_lock#3){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x3370/0x75e8 kernel/locking/lockdep.c:5144 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5761 __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 ntfs_set_state+0x1a4/0x608 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x718/0x2bac fs/ntfs3/inode.c:537 dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264 ntfs_lookup+0x108/0x1f8 fs/ntfs3/namei.c:85 __lookup_slow+0x250/0x374 fs/namei.c:1690 lookup_slow+0x60/0x84 fs/namei.c:1707 walk_component+0x280/0x36c fs/namei.c:1998 lookup_last fs/namei.c:2455 [inline] path_lookupat+0x13c/0x3d0 fs/namei.c:2479 filename_lookup+0x1d4/0x4e0 fs/namei.c:2508 user_path_at_empty+0x5c/0x1a4 fs/namei.c:2907 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir fs/open.c:545 [inline] __arm64_sys_chdir+0xc0/0x2d0 fs/open.c:545 __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+0x58/0x16c 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:591 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock/4); lock(&ni->ni_lock#3); lock(&ni->ni_lock/4); lock(&ni->ni_lock#3); *** DEADLOCK *** 2 locks held by syz-executor.3/23668: #0: ffff000135d72fe0 (&type->i_mutex_dir_key#14){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:781 [inline] #0: ffff000135d72fe0 (&type->i_mutex_dir_key#14){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706 #1: ffff000135d72d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] #1: ffff000135d72d40 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf8/0x1f8 fs/ntfs3/namei.c:84 stack backtrace: CPU: 0 PID: 23668 Comm: syz-executor.3 Not tainted 6.5.0-rc7-syzkaller-gfe4469582053 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:233 show_stack+0x2c/0x44 arch/arm64/kernel/stacktrace.c:240 __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:2068 check_noncircular+0x310/0x404 kernel/locking/lockdep.c:2195 check_prev_add kernel/locking/lockdep.c:3142 [inline] check_prevs_add kernel/locking/lockdep.c:3261 [inline] validate_chain kernel/locking/lockdep.c:3876 [inline] __lock_acquire+0x3370/0x75e8 kernel/locking/lockdep.c:5144 lock_acquire+0x23c/0x71c kernel/locking/lockdep.c:5761 __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 ntfs_set_state+0x1a4/0x608 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x718/0x2bac fs/ntfs3/inode.c:537 dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264 ntfs_lookup+0x108/0x1f8 fs/ntfs3/namei.c:85 __lookup_slow+0x250/0x374 fs/namei.c:1690 lookup_slow+0x60/0x84 fs/namei.c:1707 walk_component+0x280/0x36c fs/namei.c:1998 lookup_last fs/namei.c:2455 [inline] path_lookupat+0x13c/0x3d0 fs/namei.c:2479 filename_lookup+0x1d4/0x4e0 fs/namei.c:2508 user_path_at_empty+0x5c/0x1a4 fs/namei.c:2907 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir fs/open.c:545 [inline] __arm64_sys_chdir+0xc0/0x2d0 fs/open.c:545 __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+0x58/0x16c 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:591 ntfs3: loop3: Mark volume as dirty due to NTFS errors