ntfs3(loop3): Failed to initialize $Extend/$Reparse. ====================================================== WARNING: possible circular locking dependency detected 6.15.0-rc4-syzkaller-ge0f4c8dd9d2d #0 Not tainted ------------------------------------------------------ syz.3.248/8032 is trying to acquire lock: ffff0000fe68d9d0 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1119 but task is already holding lock: ffff0000fa2ae270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1100 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:1693 mark_as_free_ex+0x40/0x324 fs/ntfs3/fsntfs.c:2460 run_deallocate_ex+0x150/0x2bc fs/ntfs3/attrib.c:122 attr_set_size+0xbb8/0x2368 fs/ntfs3/attrib.c:753 ntfs_truncate fs/ntfs3/file.c:525 [inline] ntfs_setattr+0x458/0x910 fs/ntfs3/file.c:843 notify_change+0x9a4/0xc50 fs/attr.c:552 do_truncate+0x178/0x1f0 fs/open.c:65 vfs_truncate+0x398/0x444 fs/open.c:115 do_sys_truncate+0xe4/0x1a8 fs/open.c:138 __do_sys_truncate fs/open.c:150 [inline] __se_sys_truncate fs/open.c:148 [inline] __arm64_sys_truncate+0x5c/0x74 fs/open.c:148 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x58/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 -> #0 (&ni->file.run_lock#2){++++}-{4:4}: check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1728/0x3058 kernel/locking/lockdep.c:5235 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5866 down_read+0x58/0x2f8 kernel/locking/rwsem.c:1524 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1119 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x19f4/0x2a44 fs/ntfs3/inode.c:540 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:3679 [inline] open_last_lookups fs/namei.c:3800 [inline] path_openat+0xcc0/0x2c40 fs/namei.c:4036 do_filp_open+0x18c/0x36c fs/namei.c:4066 do_sys_openat2+0x11c/0x1b4 fs/open.c:1429 do_sys_open fs/open.c:1444 [inline] __do_sys_openat fs/open.c:1460 [inline] __se_sys_openat fs/open.c:1455 [inline] __arm64_sys_openat+0x120/0x158 fs/open.c:1455 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x58/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600 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.3.248/8032: #0: ffff0000d3538420 (sb_writers#23){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:556 #1: ffff0000dd66f918 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: inode_lock include/linux/fs.h:867 [inline] #1: ffff0000dd66f918 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: open_last_lookups fs/namei.c:3797 [inline] #1: ffff0000dd66f918 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: path_openat+0x638/0x2c40 fs/namei.c:4036 #2: ffff0000dd66f680 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1110 [inline] #2: ffff0000dd66f680 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_lookup+0xf0/0x1f0 fs/ntfs3/namei.c:84 #3: ffff0000fa2ae270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x60c/0x998 fs/ntfs3/run.c:1100 stack backtrace: CPU: 0 UID: 0 PID: 8032 Comm: syz.3.248 Not tainted 6.15.0-rc4-syzkaller-ge0f4c8dd9d2d #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:466 (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:2079 check_noncircular+0x154/0x174 kernel/locking/lockdep.c:2211 check_prev_add kernel/locking/lockdep.c:3166 [inline] check_prevs_add kernel/locking/lockdep.c:3285 [inline] validate_chain kernel/locking/lockdep.c:3909 [inline] __lock_acquire+0x1728/0x3058 kernel/locking/lockdep.c:5235 lock_acquire+0x14c/0x2e0 kernel/locking/lockdep.c:5866 down_read+0x58/0x2f8 kernel/locking/rwsem.c:1524 run_unpack_ex+0x6cc/0x998 fs/ntfs3/run.c:1119 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x19f4/0x2a44 fs/ntfs3/inode.c:540 dir_search_u+0x250/0x2a4 fs/ntfs3/dir.c:264 ntfs_lookup+0x100/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:3679 [inline] open_last_lookups fs/namei.c:3800 [inline] path_openat+0xcc0/0x2c40 fs/namei.c:4036 do_filp_open+0x18c/0x36c fs/namei.c:4066 do_sys_openat2+0x11c/0x1b4 fs/open.c:1429 do_sys_open fs/open.c:1444 [inline] __do_sys_openat fs/open.c:1460 [inline] __se_sys_openat fs/open.c:1455 [inline] __arm64_sys_openat+0x120/0x158 fs/open.c:1455 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x2b8 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+0x58/0x150 arch/arm64/kernel/entry-common.c:744 el0t_64_sync_handler+0x78/0x108 arch/arm64/kernel/entry-common.c:762 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:600