ntfs3(loop4): ino=1e, mi_enum_attr ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.913/13109 is trying to acquire lock: ffff88803dfbce70 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1135 but task is already holding lock: ffff888032dd6258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0 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_write_nested+0x3e/0x60 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c1/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a4/0x2c70 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x162/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f8/0xd50 fs/ntfs3/fsntfs.c:709 ni_create_attr_list+0x8ff/0x13d0 fs/ntfs3/frecord.c:828 ni_ins_attr_ext+0x43f/0xba0 fs/ntfs3/frecord.c:926 ni_insert_attr fs/ntfs3/frecord.c:1093 [inline] ni_insert_resident fs/ntfs3/frecord.c:1477 [inline] ni_add_name+0x6df/0xc90 fs/ntfs3/frecord.c:2923 ntfs_link_inode+0x132/0x180 fs/ntfs3/inode.c:1738 ntfs_link+0x118/0x280 fs/ntfs3/namei.c:146 vfs_link+0x518/0x6e0 fs/namei.c:5646 do_linkat+0x283/0x5a0 fs/namei.c:5716 __do_sys_link fs/namei.c:5750 [inline] __se_sys_link fs/namei.c:5748 [inline] __x64_sys_link+0x82/0x90 fs/namei.c:5748 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f -> #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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x107/0x340 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x238b/0x3860 fs/ntfs3/inode.c:542 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:4413 [inline] open_last_lookups fs/namei.c:4540 [inline] path_openat+0x13aa/0x3df0 fs/namei.c:4784 do_filp_open+0x1fa/0x410 fs/namei.c:4814 do_sys_openat2+0x121/0x200 fs/open.c:1430 do_sys_open fs/open.c:1436 [inline] __do_sys_openat fs/open.c:1452 [inline] __se_sys_openat fs/open.c:1447 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1447 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f 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.4.913/13109: #0: ffff888035d9c480 (sb_writers#20){++++}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499 #1: ffff88805d63d838 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: inode_lock include/linux/fs.h:1027 [inline] #1: ffff88805d63d838 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: open_last_lookups fs/namei.c:4537 [inline] #1: ffff88805d63d838 (&type->i_mutex_dir_key#12){++++}-{4:4}, at: path_openat+0xb53/0x3df0 fs/namei.c:4784 #2: ffff88805d63d580 (&ni->ni_lock#3/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline] #2: ffff88805d63d580 (&ni->ni_lock#3/6){+.+.}-{4:4}, at: ntfs_lookup+0xee/0x1f0 fs/ntfs3/namei.c:84 #3: ffff888032dd6258 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0 fs/ntfs3/run.c:1116 stack backtrace: CPU: 1 UID: 0 PID: 13109 Comm: syz.4.913 Not tainted syzkaller #0 PREEMPT_{RT,(full)} Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_circular_bug+0x2e2/0x300 kernel/locking/lockdep.c:2043 check_noncircular+0x12e/0x150 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+0x15a6/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x107/0x340 kernel/locking/lockdep.c:5868 down_read+0x97/0x1f0 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1135 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x238b/0x3860 fs/ntfs3/inode.c:542 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:4413 [inline] open_last_lookups fs/namei.c:4540 [inline] path_openat+0x13aa/0x3df0 fs/namei.c:4784 do_filp_open+0x1fa/0x410 fs/namei.c:4814 do_sys_openat2+0x121/0x200 fs/open.c:1430 do_sys_open fs/open.c:1436 [inline] __do_sys_openat fs/open.c:1452 [inline] __se_sys_openat fs/open.c:1447 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1447 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xec/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f058e18f749 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f058c3d5038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f058e3e6090 RCX: 00007f058e18f749 RDX: 0000000000187842 RSI: 0000200000000200 RDI: ffffffffffffff9c RBP: 00007f058e213f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f058e3e6128 R14: 00007f058e3e6090 R15: 00007ffef4daa2d8