====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.4.125/6667 is trying to acquire lock: ffff88807a5f4270 (&wnd->rw_lock){++++}-{3:3}, at: ntfs_look_for_free_space+0xd4/0x600 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff88805da29070 (&ni->file.run_lock#2){++++}-{3:3}, at: ntfs_extend_mft+0x13e/0x450 fs/ntfs3/fsntfs.c:511 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->file.run_lock#2){++++}-{3:3}: down_read+0x46/0x2e0 kernel/locking/rwsem.c:1520 run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1122 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0x22e3/0x3760 fs/ntfs3/inode.c:534 ntfs_dir_emit fs/ntfs3/dir.c:338 [inline] ntfs_read_hdr+0x7d4/0xc30 fs/ntfs3/dir.c:386 ntfs_readdir+0xaf4/0xe60 fs/ntfs3/dir.c:497 iterate_dir+0x1c2/0x580 fs/readdir.c:106 __do_sys_getdents64 fs/readdir.c:405 [inline] __se_sys_getdents64+0xe9/0x260 fs/readdir.c:390 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x68/0xd2 -> #0 (&wnd->rw_lock){++++}-{3:3}: check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754 down_write_nested+0x9e/0x1f0 kernel/locking/rwsem.c:1689 ntfs_look_for_free_space+0xd4/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c2/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a0/0x2c60 fs/ntfs3/attrib.c:575 ntfs_extend_mft+0x163/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f6/0xd40 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x524/0x3680 fs/ntfs3/inode.c:1344 ntfs_atomic_open+0x3f4/0x520 fs/ntfs3/namei.c:430 atomic_open fs/namei.c:3359 [inline] lookup_open fs/namei.c:3467 [inline] open_last_lookups fs/namei.c:3564 [inline] path_openat+0xf27/0x3190 fs/namei.c:3794 do_filp_open+0x1c5/0x3d0 fs/namei.c:3824 file_open_name fs/open.c:1366 [inline] filp_open+0x177/0x1d0 fs/open.c:1386 do_coredump+0x1c22/0x2480 fs/coredump.c:774 get_signal+0x1133/0x1400 kernel/signal.c:2888 arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210 irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315 exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); lock(&ni->file.run_lock#2); lock(&wnd->rw_lock); *** DEADLOCK *** 5 locks held by syz.4.125/6667: #0: ffff88807a5f2418 (sb_writers#22){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412 #1: ffff888076ea03b0 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline] #1: ffff888076ea03b0 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: open_last_lookups fs/namei.c:3561 [inline] #1: ffff888076ea03b0 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: path_openat+0x7c6/0x3190 fs/namei.c:3794 #2: ffff888076ea0100 (&ni->ni_lock#2/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1124 [inline] #2: ffff888076ea0100 (&ni->ni_lock#2/6){+.+.}-{3:3}, at: ntfs_create_inode+0x171/0x3680 fs/ntfs3/inode.c:1258 #3: ffff88807a5f4128 (&wnd->rw_lock/1){+.+.}-{3:3}, at: ntfs_look_free_mft+0x164/0xd40 fs/ntfs3/fsntfs.c:571 #4: ffff88805da29070 (&ni->file.run_lock#2){++++}-{3:3}, at: ntfs_extend_mft+0x13e/0x450 fs/ntfs3/fsntfs.c:511 stack backtrace: CPU: 0 PID: 6667 Comm: syz.4.125 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Call Trace: dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106 check_noncircular+0x2bd/0x3c0 kernel/locking/lockdep.c:2187 check_prev_add kernel/locking/lockdep.c:3134 [inline] check_prevs_add kernel/locking/lockdep.c:3253 [inline] validate_chain kernel/locking/lockdep.c:3869 [inline] __lock_acquire+0x2ddb/0x7c80 kernel/locking/lockdep.c:5137 lock_acquire+0x197/0x410 kernel/locking/lockdep.c:5754 down_write_nested+0x9e/0x1f0 kernel/locking/rwsem.c:1689 ntfs_look_for_free_space+0xd4/0x600 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x1c2/0x6d0 fs/ntfs3/attrib.c:159 attr_set_size+0x14a0/0x2c60 fs/ntfs3/attrib.c:575 ntfs_extend_mft+0x163/0x450 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x5f6/0xd40 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x524/0x3680 fs/ntfs3/inode.c:1344 ntfs_atomic_open+0x3f4/0x520 fs/ntfs3/namei.c:430 atomic_open fs/namei.c:3359 [inline] lookup_open fs/namei.c:3467 [inline] open_last_lookups fs/namei.c:3564 [inline] path_openat+0xf27/0x3190 fs/namei.c:3794 do_filp_open+0x1c5/0x3d0 fs/namei.c:3824 file_open_name fs/open.c:1366 [inline] filp_open+0x177/0x1d0 fs/open.c:1386 do_coredump+0x1c22/0x2480 fs/coredump.c:774 get_signal+0x1133/0x1400 kernel/signal.c:2888 arch_do_signal_or_restart+0x9c/0x7b0 arch/x86/kernel/signal.c:310 exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174 exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210 irqentry_exit_to_user_mode+0x9/0x40 kernel/entry/common.c:315 exc_page_fault+0x8f/0x110 arch/x86/mm/fault.c:1524 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:608 RIP: 0033:0x7f91da98f751 Code: 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 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f RSP: 002b:fffffffffffffe70 EFLAGS: 00010217 RAX: 0000000000000000 RBX: 00007f91dabe6180 RCX: 00007f91da98f749 RDX: 0000000000000000 RSI: fffffffffffffe70 RDI: 0000000000008000 RBP: 00007f91daa13f91 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000000000 R13: 00007f91dabe6218 R14: 00007f91dabe6180 R15: 00007fff8c8affd8