ntfs3(loop8): Failed to initialize $Extend/$Reparse. ntfs3( ntfs3(loop8): ino=1b, mi_enum_attr ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.8.279/8317 is trying to acquire lock: ffff0000ff68a618 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1135 but task is already holding lock: ffff0000d4c28278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1116 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&wnd->rw_lock){++++}-{4:4}: down_read_nested+0x5c/0x30c kernel/locking/rwsem.c:1662 run_unpack_ex+0x540/0x998 fs/ntfs3/run.c:1105 attr_load_runs fs/ntfs3/attrib.c:81 [inline] attr_collapse_range+0x904/0x111c fs/ntfs3/attrib.c:1970 ntfs_fallocate+0x634/0xdd4 fs/ntfs3/file.c:690 vfs_fallocate+0x52c/0x668 fs/open.c:339 ksys_fallocate fs/open.c:363 [inline] __do_sys_fallocate fs/open.c:368 [inline] __se_sys_fallocate fs/open.c:366 [inline] __arm64_sys_fallocate+0xbc/0x10c fs/open.c:366 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743 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+0x140/0x2e0 kernel/locking/lockdep.c:5868 down_read+0x58/0x308 kernel/locking/rwsem.c:1537 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x1a28/0x2ad0 fs/ntfs3/inode.c:542 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x10c/0x2fc fs/namei.c:1747 __start_renaming+0x164/0x3c4 fs/namei.c:3812 do_renameat2+0x344/0x7c0 fs/namei.c:6022 __do_sys_renameat2 fs/namei.c:6077 [inline] __se_sys_renameat2 fs/namei.c:6074 [inline] __arm64_sys_renameat2+0xd8/0xf4 fs/namei.c:6074 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743 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 *** 4 locks held by syz.8.279/8317: #0: ffff0000dad7a420 (sb_writers#19){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:499 #1: ffff0000ff68e988 (&type->i_mutex_dir_key#15/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1072 [inline] #1: ffff0000ff68e988 (&type->i_mutex_dir_key#15/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3712 [inline] #1: ffff0000ff68e988 (&type->i_mutex_dir_key#15/1){+.+.}-{4:4}, at: __start_renaming+0x140/0x3c4 fs/namei.c:3808 #2: ffff0000ff68e6f0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline] #2: ffff0000ff68e6f0 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_lookup+0xf0/0x1f0 fs/ntfs3/namei.c:84 #3: ffff0000d4c28278 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1116 stack backtrace: CPU: 0 UID: 0 PID: 8317 Comm: syz.8.279 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+0x140/0x2e0 kernel/locking/lockdep.c:5868 down_read+0x58/0x308 kernel/locking/rwsem.c:1537 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x1a28/0x2ad0 fs/ntfs3/inode.c:542 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x10c/0x2fc fs/namei.c:1747 __start_renaming+0x164/0x3c4 fs/namei.c:3812 do_renameat2+0x344/0x7c0 fs/namei.c:6022 __do_sys_renameat2 fs/namei.c:6077 [inline] __se_sys_renameat2 fs/namei.c:6074 [inline] __arm64_sys_renameat2+0xd8/0xf4 fs/namei.c:6074 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 trusted_key: syz.8.279 sent an empty control message without MSG_MORE.