====================================================== WARNING: possible circular locking dependency detected 6.6.0-rc3-syzkaller-00055-g9ed22ae6be81 #0 Not tainted ------------------------------------------------------ syz-executor.4/13812 is trying to acquire lock: ffff88803643ad40 (&ni->ni_lock){+.+.}-{3:3}, at: ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 but task is already holding lock: ffff88803643b4a0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] ffff88803643b4a0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_unlink_inode+0x321/0x7d0 fs/ntfs3/inode.c:1754 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 kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 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+0xe41/0x1070 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 handle_truncate fs/namei.c:3298 [inline] do_open fs/namei.c:3643 [inline] path_openat+0x2959/0x3180 fs/namei.c:3796 do_filp_open+0x234/0x490 fs/namei.c:3823 do_sys_openat2+0x13e/0x1d0 fs/open.c:1422 do_sys_open fs/open.c:1437 [inline] __do_sys_creat fs/open.c:1513 [inline] __se_sys_creat fs/open.c:1507 [inline] __x64_sys_creat+0x123/0x160 fs/open.c:1507 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){+.+.}-{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 kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 ni_remove_name+0x2c0/0x9b0 fs/ntfs3/frecord.c:2926 ntfs_unlink_inode+0x403/0x7d0 fs/ntfs3/inode.c:1766 ntfs_unlink+0x33/0x50 fs/ntfs3/namei.c:186 vfs_unlink+0x35d/0x5f0 fs/namei.c:4332 do_unlinkat+0x4a7/0x950 fs/namei.c:4398 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4434 [inline] __x64_sys_unlinkat+0xce/0xf0 fs/namei.c:4434 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); lock(&ni->ni_lock/4); lock(&ni->ni_lock); *** DEADLOCK *** 5 locks held by syz-executor.4/13812: #0: ffff88807c59a410 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x3f/0x90 fs/namespace.c:403 #1: ffff88803643a880 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:837 [inline] #1: ffff88803643a880 (&type->i_mutex_dir_key#13/1){+.+.}-{3:3}, at: do_unlinkat+0x26a/0x950 fs/namei.c:4383 #2: ffff88803643b740 (&sb->s_type->i_mutex_key#27){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:802 [inline] #2: ffff88803643b740 (&sb->s_type->i_mutex_key#27){+.+.}-{3:3}, at: vfs_unlink+0xe4/0x5f0 fs/namei.c:4321 #3: ffff88803643a5e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1129 [inline] #3: ffff88803643a5e0 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_unlink+0x28/0x50 fs/ntfs3/namei.c:184 #4: ffff88803643b4a0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] #4: ffff88803643b4a0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_unlink_inode+0x321/0x7d0 fs/ntfs3/inode.c:1754 stack backtrace: CPU: 0 PID: 13812 Comm: syz-executor.4 Not tainted 6.6.0-rc3-syzkaller-00055-g9ed22ae6be81 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/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 kernel/locking/mutex.c:603 [inline] __mutex_lock+0x136/0xd60 kernel/locking/mutex.c:747 ntfs_set_state+0x212/0x730 fs/ntfs3/fsntfs.c:946 ni_remove_name+0x2c0/0x9b0 fs/ntfs3/frecord.c:2926 ntfs_unlink_inode+0x403/0x7d0 fs/ntfs3/inode.c:1766 ntfs_unlink+0x33/0x50 fs/ntfs3/namei.c:186 vfs_unlink+0x35d/0x5f0 fs/namei.c:4332 do_unlinkat+0x4a7/0x950 fs/namei.c:4398 __do_sys_unlinkat fs/namei.c:4441 [inline] __se_sys_unlinkat fs/namei.c:4434 [inline] __x64_sys_unlinkat+0xce/0xf0 fs/namei.c:4434 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:0x7fde8fe7cae9 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:00007fde90c4c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000107 RAX: ffffffffffffffda RBX: 00007fde8ff9bf80 RCX: 00007fde8fe7cae9 RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000004 RBP: 00007fde8fec847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007fde8ff9bf80 R15: 00007ffca5a539c8 ntfs3: loop4: ino=3, ntfs3_write_inode failed, -22.