====================================================== WARNING: possible circular locking dependency detected 6.6.0-rc1-syzkaller-00240-gf0b0d403eabb #0 Not tainted ------------------------------------------------------ syz-executor.4/11153 is trying to acquire lock: ffff888031638fc0 (&ni->ni_lock#2){+.+.}-{3:3}, at: ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 but task is already holding lock: ffff888078a68860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] ffff888078a68860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf9/0x1f0 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+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] mi_read+0x2e1/0x5a0 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:70 [inline] ntfs_iget5+0x47d/0x38e0 fs/ntfs3/inode.c:532 ni_update_parent+0x806/0xc80 fs/ntfs3/frecord.c:3212 ni_write_inode+0xe48/0x1080 fs/ntfs3/frecord.c:3312 ntfs_truncate fs/ntfs3/file.c:407 [inline] ntfs3_setattr+0x725/0xae0 fs/ntfs3/file.c:682 notify_change+0xb99/0xe60 fs/attr.c:499 do_truncate+0x220/0x300 fs/open.c:66 do_sys_ftruncate+0x2f3/0x390 fs/open.c:194 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&ni->ni_lock#2){+.+.}-{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:3868 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x571/0x38e0 fs/ntfs3/inode.c:539 dir_search_u+0x2fa/0x3a0 fs/ntfs3/dir.c:264 ntfs_lookup+0x106/0x1f0 fs/ntfs3/namei.c:85 __lookup_slow+0x282/0x3e0 fs/namei.c:1693 lookup_slow+0x53/0x70 fs/namei.c:1710 walk_component+0x2d0/0x400 fs/namei.c:2001 lookup_last fs/namei.c:2458 [inline] path_lookupat+0x16f/0x450 fs/namei.c:2482 filename_lookup+0x255/0x610 fs/namei.c:2511 user_path_at_empty+0x44/0x180 fs/namei.c:2910 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir+0xbf/0x220 fs/open.c:545 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock/4); lock(&ni->ni_lock#2); lock(&ni->ni_lock/4); lock(&ni->ni_lock#2); *** DEADLOCK *** 2 locks held by syz-executor.4/11153: #0: ffff888078a68b00 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:812 [inline] #0: ffff888078a68b00 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: lookup_slow+0x45/0x70 fs/namei.c:1709 #1: ffff888078a68860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] #1: ffff888078a68860 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf9/0x1f0 fs/ntfs3/namei.c:84 stack backtrace: CPU: 1 PID: 11153 Comm: syz-executor.4 Not tainted 6.6.0-rc1-syzkaller-00240-gf0b0d403eabb #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 check_noncircular+0x375/0x4a0 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:3868 [inline] __lock_acquire+0x39ff/0x7f70 kernel/locking/lockdep.c:5136 lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5753 __mutex_lock_common+0x1d8/0x2530 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x1b/0x20 kernel/locking/mutex.c:799 ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x571/0x38e0 fs/ntfs3/inode.c:539 dir_search_u+0x2fa/0x3a0 fs/ntfs3/dir.c:264 ntfs_lookup+0x106/0x1f0 fs/ntfs3/namei.c:85 __lookup_slow+0x282/0x3e0 fs/namei.c:1693 lookup_slow+0x53/0x70 fs/namei.c:1710 walk_component+0x2d0/0x400 fs/namei.c:2001 lookup_last fs/namei.c:2458 [inline] path_lookupat+0x16f/0x450 fs/namei.c:2482 filename_lookup+0x255/0x610 fs/namei.c:2511 user_path_at_empty+0x44/0x180 fs/namei.c:2910 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir+0xbf/0x220 fs/open.c:545 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f955107cae9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f9551dd00c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000050 RAX: ffffffffffffffda RBX: 00007f955119bf80 RCX: 00007f955107cae9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000040 RBP: 00007f95510c847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f955119bf80 R15: 00007ffc87609d88 ntfs3: loop4: Mark volume as dirty due to NTFS errors