ntfs3(loop4): Mark volume as dirty due to NTFS errors ntfs3(loop4): Failed to load $Extend (-22). ntfs3(loop4): Failed to initialize $Extend. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.1065/9878 is trying to acquire lock: ffff0000dc5aad60 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1124 but task is already holding lock: ffff0000e3ea4270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1105 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&wnd->rw_lock){++++}-{4:4}: down_write_nested+0x58/0xcc kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xbc/0x560 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x198/0x620 fs/ntfs3/attrib.c:159 attr_set_size+0x1064/0x2368 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x130/0x394 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x500/0xb1c fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x394/0x27d0 fs/ntfs3/inode.c:1302 ntfs_mkdir+0x54/0x70 fs/ntfs3/namei.c:215 vfs_mkdir+0x284/0x424 fs/namei.c:4453 do_mkdirat+0x1f8/0x4c8 fs/namei.c:4486 __do_sys_mkdirat fs/namei.c:4503 [inline] __se_sys_mkdirat fs/namei.c:4501 [inline] __arm64_sys_mkdirat+0x8c/0xa4 fs/namei.c:4501 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 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+0x5c/0x254 arch/arm64/kernel/entry-common.c:746 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 -> #0 (&ni->file.run_lock#2){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 down_read+0x58/0x2f8 kernel/locking/rwsem.c:1537 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1124 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x1a00/0x2a90 fs/ntfs3/inode.c:541 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 __lookup_slow+0x254/0x378 fs/namei.c:1816 lookup_slow+0x5c/0x80 fs/namei.c:1833 walk_component+0x270/0x364 fs/namei.c:2151 lookup_last fs/namei.c:2652 [inline] path_lookupat+0x13c/0x3d0 fs/namei.c:2676 filename_lookup+0x1ac/0x454 fs/namei.c:2705 user_path_at+0x50/0x74 fs/namei.c:3215 do_sys_truncate+0xac/0x1a8 fs/open.c:139 __do_sys_truncate fs/open.c:153 [inline] __se_sys_truncate fs/open.c:151 [inline] __arm64_sys_truncate+0x5c/0x74 fs/open.c:151 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 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+0x5c/0x254 arch/arm64/kernel/entry-common.c:746 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&wnd->rw_lock); lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); rlock(&ni->file.run_lock#2); *** DEADLOCK *** 3 locks held by syz.4.1065/9878: #0: ffff0000dc641228 (&type->i_mutex_dir_key#17){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:995 [inline] #0: ffff0000dc641228 (&type->i_mutex_dir_key#17){++++}-{4:4}, at: lookup_slow+0x4c/0x80 fs/namei.c:1832 #1: ffff0000dc640f90 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline] #1: ffff0000dc640f90 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_lookup+0xf0/0x1f0 fs/ntfs3/namei.c:84 #2: ffff0000e3ea4270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1105 stack backtrace: CPU: 1 UID: 0 PID: 9878 Comm: syz.4.1065 Not tainted syzkaller #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 dump_stack+0x1c/0x28 lib/dump_stack.c:129 print_circular_bug+0x324/0x32c kernel/locking/lockdep.c:2043 check_noncircular+0x154/0x174 kernel/locking/lockdep.c:2175 check_prev_add kernel/locking/lockdep.c:3165 [inline] check_prevs_add kernel/locking/lockdep.c:3284 [inline] validate_chain kernel/locking/lockdep.c:3908 [inline] __lock_acquire+0x1774/0x30a4 kernel/locking/lockdep.c:5237 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5868 down_read+0x58/0x2f8 kernel/locking/rwsem.c:1537 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1124 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x1a00/0x2a90 fs/ntfs3/inode.c:541 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 __lookup_slow+0x254/0x378 fs/namei.c:1816 lookup_slow+0x5c/0x80 fs/namei.c:1833 walk_component+0x270/0x364 fs/namei.c:2151 lookup_last fs/namei.c:2652 [inline] path_lookupat+0x13c/0x3d0 fs/namei.c:2676 filename_lookup+0x1ac/0x454 fs/namei.c:2705 user_path_at+0x50/0x74 fs/namei.c:3215 do_sys_truncate+0xac/0x1a8 fs/open.c:139 __do_sys_truncate fs/open.c:153 [inline] __se_sys_truncate fs/open.c:151 [inline] __arm64_sys_truncate+0x5c/0x74 fs/open.c:151 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 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+0x5c/0x254 arch/arm64/kernel/entry-common.c:746 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:765 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596