loop1: detected capacity change from 0 to 4096 ntfs3(loop1): Different NTFS sector size (1024) and media sector size (512). ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.923/13382 is trying to acquire lock: ffff88805d804258 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xd3/0x600 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff888039632fb0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/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){++++}-{4:4}: 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 ntfs_dir_emit fs/ntfs3/dir.c:336 [inline] ntfs_read_hdr+0x7cf/0xc30 fs/ntfs3/dir.c:384 ntfs_readdir+0xa5f/0xdd0 fs/ntfs3/dir.c:495 iterate_dir+0x3a5/0x580 fs/readdir.c:108 __do_sys_getdents64 fs/readdir.c:410 [inline] __se_sys_getdents64+0xe4/0x260 fs/readdir.c:396 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 (&wnd->rw_lock){++++}-{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_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 ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1305 ntfs_mkdir+0x3d/0x50 fs/ntfs3/namei.c:215 vfs_mkdir+0x52d/0x5d0 fs/namei.c:5130 do_mkdirat+0x27a/0x4b0 fs/namei.c:5164 __do_sys_mkdirat fs/namei.c:5186 [inline] __se_sys_mkdirat fs/namei.c:5184 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:5184 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(&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.1.923/13382: #0: ffff88805ff2a480 (sb_writers#14){++++}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:499 #1: ffff888039630b58 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:1072 [inline] #1: ffff888039630b58 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: __start_dirop fs/namei.c:2864 [inline] #1: ffff888039630b58 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: start_dirop fs/namei.c:2875 [inline] #1: ffff888039630b58 (&type->i_mutex_dir_key#10/1){+.+.}-{4:4}, at: filename_create+0x1fb/0x360 fs/namei.c:4879 #2: ffff8880396308a0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1132 [inline] #2: ffff8880396308a0 (&ni->ni_lock#2/6){+.+.}-{4:4}, at: ntfs_create_inode+0x16e/0x32a0 fs/ntfs3/inode.c:1213 #3: ffff88805d804120 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x163/0xd50 fs/ntfs3/fsntfs.c:571 #4: ffff888039632fb0 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x13d/0x450 fs/ntfs3/fsntfs.c:511 stack backtrace: CPU: 0 UID: 0 PID: 13382 Comm: syz.1.923 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_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 ntfs_create_inode+0x590/0x32a0 fs/ntfs3/inode.c:1305 ntfs_mkdir+0x3d/0x50 fs/ntfs3/namei.c:215 vfs_mkdir+0x52d/0x5d0 fs/namei.c:5130 do_mkdirat+0x27a/0x4b0 fs/namei.c:5164 __do_sys_mkdirat fs/namei.c:5186 [inline] __se_sys_mkdirat fs/namei.c:5184 [inline] __x64_sys_mkdirat+0x87/0xa0 fs/namei.c:5184 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:0x7f84f4e7de97 Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 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:00007f84f30dde68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 00007f84f30ddef0 RCX: 00007f84f4e7de97 RDX: 00000000000001ff RSI: 0000200000000280 RDI: 00000000ffffff9c RBP: 0000200000000000 R08: 0000200000000080 R09: 0000000000000000 R10: 0000200000000000 R11: 0000000000000246 R12: 0000200000000280 R13: 00007f84f30ddeb0 R14: 0000000000000000 R15: 0000000000000000 ntfs3(loop1): ino=0, attr_set_size ntfs3(loop1): ino=0, attr_set_size ntfs3(loop1): ino=0, attr_set_size