ntfs3(loop1): Different NTFS sector size (1024) and media sector size (512). ====================================================== WARNING: possible circular locking dependency detected 6.16.0-syzkaller-11699-g7e161a991ea7 #0 Not tainted ------------------------------------------------------ syz.1.12379/2672 is trying to acquire lock: ffff88807eb78270 (&wnd->rw_lock){++++}-{4:4}, at: ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 but task is already holding lock: ffff888012da4b20 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x137/0x430 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+0x9b/0x480 kernel/locking/rwsem.c:1537 run_unpack_ex+0x671/0x740 fs/ntfs3/run.c:1119 ntfs_read_mft fs/ntfs3/inode.c:401 [inline] ntfs_iget5+0xd97/0x3ab0 fs/ntfs3/inode.c:540 dir_search_u+0x163/0x3a0 fs/ntfs3/dir.c:264 ntfs_lookup+0x1c5/0x2a0 fs/ntfs3/namei.c:85 lookup_one_qstr_excl+0x1d1/0x250 fs/namei.c:1697 filename_create+0x1e7/0x4a0 fs/namei.c:4140 do_mknodat+0x18a/0x5d0 fs/namei.c:4272 __do_sys_mknodat fs/namei.c:4313 [inline] __se_sys_mknodat fs/namei.c:4310 [inline] __x64_sys_mknodat+0xaf/0xe0 fs/namei.c:4310 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825 down_write_nested+0x96/0x210 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x3ff/0x6f0 fs/ntfs3/attrib.c:159 attr_set_size+0x15ae/0x2c50 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x15c/0x430 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x695/0xe10 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x413/0x3fa0 fs/ntfs3/inode.c:1296 ntfs_mknod+0x3d/0x50 fs/ntfs3/namei.c:120 vfs_mknod+0x5da/0x8e0 fs/namei.c:4235 do_mknodat+0x30f/0x5d0 fs/namei.c:4295 __do_sys_mknod fs/namei.c:4318 [inline] __se_sys_mknod fs/namei.c:4316 [inline] __x64_sys_mknod+0x87/0xb0 fs/namei.c:4316 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 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.12379/2672: #0: ffff8880532dc428 (sb_writers#24){.+.+}-{0:0}, at: filename_create+0x10e/0x4a0 fs/namei.c:4132 #1: ffff888012da5bb8 (&type->i_mutex_dir_key#15/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:914 [inline] #1: ffff888012da5bb8 (&type->i_mutex_dir_key#15/1){+.+.}-{4:4}, at: filename_create+0x1bb/0x4a0 fs/namei.c:4139 #2: ffff888012da5920 (&ni->ni_lock#3/6){+.+.}-{4:4}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1118 [inline] #2: ffff888012da5920 (&ni->ni_lock#3/6){+.+.}-{4:4}, at: ntfs_create_inode+0x1e29/0x3fa0 fs/ntfs3/inode.c:1204 #3: ffff88807eb78128 (&wnd->rw_lock/1){+.+.}-{4:4}, at: ntfs_look_free_mft+0x349/0xe10 fs/ntfs3/fsntfs.c:571 #4: ffff888012da4b20 (&ni->file.run_lock#2){++++}-{4:4}, at: ntfs_extend_mft+0x137/0x430 fs/ntfs3/fsntfs.c:511 stack backtrace: CPU: 0 UID: 0 PID: 2672 Comm: syz.1.12379 Not tainted 6.16.0-syzkaller-11699-g7e161a991ea7 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025 Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_circular_bug+0x275/0x350 kernel/locking/lockdep.c:2043 check_noncircular+0x14c/0x170 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+0x12a6/0x1ce0 kernel/locking/lockdep.c:5237 lock_acquire kernel/locking/lockdep.c:5868 [inline] lock_acquire+0x179/0x350 kernel/locking/lockdep.c:5825 down_write_nested+0x96/0x210 kernel/locking/rwsem.c:1706 ntfs_look_for_free_space+0xcc/0x720 fs/ntfs3/fsntfs.c:362 attr_allocate_clusters+0x3ff/0x6f0 fs/ntfs3/attrib.c:159 attr_set_size+0x15ae/0x2c50 fs/ntfs3/attrib.c:574 ntfs_extend_mft+0x15c/0x430 fs/ntfs3/fsntfs.c:512 ntfs_look_free_mft+0x695/0xe10 fs/ntfs3/fsntfs.c:709 ntfs_create_inode+0x413/0x3fa0 fs/ntfs3/inode.c:1296 ntfs_mknod+0x3d/0x50 fs/ntfs3/namei.c:120 vfs_mknod+0x5da/0x8e0 fs/namei.c:4235 do_mknodat+0x30f/0x5d0 fs/namei.c:4295 __do_sys_mknod fs/namei.c:4318 [inline] __se_sys_mknod fs/namei.c:4316 [inline] __x64_sys_mknod+0x87/0xb0 fs/namei.c:4316 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x4c0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fb245f8eb69 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:00007fb246e7c038 EFLAGS: 00000246 ORIG_RAX: 0000000000000085 RAX: ffffffffffffffda RBX: 00007fb2461b5fa0 RCX: 00007fb245f8eb69 RDX: 0000000000000703 RSI: 000000000000c000 RDI: 0000200000000040 RBP: 00007fb246011df1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007fb2461b5fa0 R15: 00007ffd66d6d998