loop2: detected capacity change from 0 to 4096 ntfs3(loop2): Different NTFS sector size (4096) and media sector size (512). ntfs3(loop2): Mark volume as dirty due to NTFS errors ntfs3(loop2): Failed to initialize $Extend/$Reparse. ntfs3(loop2): ino=1b, mi_enum_attr ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.2.3051/19411 is trying to acquire lock: ffff88805dae9040 (&ni->file.run_lock#2){++++}-{4:4}, at: run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1124 but task is already holding lock: ffff88803231c270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0 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}: lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_write_nested+0x9d/0x200 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:826 ni_ins_attr_ext+0x43e/0xb50 fs/ntfs3/frecord.c:924 ni_insert_attr fs/ntfs3/frecord.c:1091 [inline] ni_insert_resident fs/ntfs3/frecord.c:1475 [inline] ni_add_name+0x6df/0xc90 fs/ntfs3/frecord.c:2987 ni_rename+0x4a/0x100 fs/ntfs3/frecord.c:3026 ntfs_rename+0x735/0xbf0 fs/ntfs3/namei.c:332 vfs_rename+0xb34/0xe80 fs/namei.c:5216 do_renameat2+0x6a2/0xa50 fs/namei.c:5364 __do_sys_rename fs/namei.c:5411 [inline] __se_sys_rename fs/namei.c:5409 [inline] __x64_sys_rename+0x82/0x90 fs/namei.c:5409 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1124 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x232b/0x37e0 fs/ntfs3/inode.c:541 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:3774 [inline] open_last_lookups fs/namei.c:3895 [inline] path_openat+0x1101/0x3830 fs/namei.c:4131 do_filp_open+0x1fa/0x410 fs/namei.c:4161 do_sys_openat2+0x121/0x1c0 fs/open.c:1437 do_sys_open fs/open.c:1452 [inline] __do_sys_openat fs/open.c:1468 [inline] __se_sys_openat fs/open.c:1463 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1463 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 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 *** 3 locks held by syz.2.3051/19411: #0: ffff88807a1e6240 (&type->i_mutex_dir_key#13){++++}-{4:4}, at: inode_lock_shared include/linux/fs.h:995 [inline] #0: ffff88807a1e6240 (&type->i_mutex_dir_key#13){++++}-{4:4}, at: open_last_lookups fs/namei.c:3894 [inline] #0: ffff88807a1e6240 (&type->i_mutex_dir_key#13){++++}-{4:4}, at: path_openat+0x8cb/0x3830 fs/namei.c:4131 #1: ffff88807a1e5fa8 (&ni->ni_lock/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline] #1: ffff88807a1e5fa8 (&ni->ni_lock/6){+.+.}-{4:4}, at: ntfs_lookup+0xee/0x1f0 fs/ntfs3/namei.c:84 #2: ffff88803231c270 (&wnd->rw_lock){++++}-{4:4}, at: run_unpack_ex+0x701/0xba0 fs/ntfs3/run.c:1105 stack backtrace: CPU: 1 UID: 0 PID: 19411 Comm: syz.2.3051 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043 check_noncircular+0x134/0x160 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+0xb9b/0x2140 kernel/locking/lockdep.c:3908 __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237 lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868 down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537 run_unpack_ex+0x7e5/0xba0 fs/ntfs3/run.c:1124 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x232b/0x37e0 fs/ntfs3/inode.c:541 dir_search_u+0x1df/0x2c0 fs/ntfs3/dir.c:264 ntfs_lookup+0xfb/0x1f0 fs/ntfs3/namei.c:85 lookup_open fs/namei.c:3774 [inline] open_last_lookups fs/namei.c:3895 [inline] path_openat+0x1101/0x3830 fs/namei.c:4131 do_filp_open+0x1fa/0x410 fs/namei.c:4161 do_sys_openat2+0x121/0x1c0 fs/open.c:1437 do_sys_open fs/open.c:1452 [inline] __do_sys_openat fs/open.c:1468 [inline] __se_sys_openat fs/open.c:1463 [inline] __x64_sys_openat+0x138/0x170 fs/open.c:1463 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f101178eec9 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:00007f10125f9038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101 RAX: ffffffffffffffda RBX: 00007f10119e5fa0 RCX: 00007f101178eec9 RDX: 0000000000000000 RSI: 00002000000000c0 RDI: ffffffffffffff9c RBP: 00007f1011811f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f10119e6038 R14: 00007f10119e5fa0 R15: 00007ffc7c99f6b8