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.
======================================================
WARNING: possible circular locking dependency detected
6.6.100-syzkaller #0 Not tainted
------------------------------------------------------
syz.2.28/5999 is trying to acquire lock:
ffff88804ac7e190 (&ni->file.run_lock#2){++++}-{3:3}, at: run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117

but task is already holding lock:
ffff88807fac8270 (&wnd->rw_lock){++++}-{3:3}, at: run_unpack_ex+0x702/0xba0 fs/ntfs3/run.c:1098

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #1 (&wnd->rw_lock){++++}-{3:3}:
       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:1338
       ntfs_symlink+0xda/0x120 fs/ntfs3/namei.c:208
       vfs_symlink+0x138/0x2b0 fs/namei.c:4473
       do_symlinkat+0x1b2/0x3f0 fs/namei.c:4499
       __do_sys_symlink fs/namei.c:4520 [inline]
       __se_sys_symlink fs/namei.c:4518 [inline]
       __x64_sys_symlink+0x7e/0x90 fs/namei.c:4518
       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 (&ni->file.run_lock#2){++++}-{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_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
       run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117
       ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
       ntfs_iget5+0x22e3/0x3750 fs/ntfs3/inode.c:533
       dir_search_u+0x1e0/0x2b0 fs/ntfs3/dir.c:264
       ntfs_atomic_open+0x23b/0x520 fs/ntfs3/namei.c:412
       atomic_open fs/namei.c:3351 [inline]
       lookup_open fs/namei.c:3459 [inline]
       open_last_lookups fs/namei.c:3556 [inline]
       path_openat+0xf27/0x3190 fs/namei.c:3786
       do_filp_open+0x1c5/0x3d0 fs/namei.c:3816
       do_sys_openat2+0x12c/0x1c0 fs/open.c:1419
       do_sys_open fs/open.c:1434 [inline]
       __do_sys_openat fs/open.c:1450 [inline]
       __se_sys_openat fs/open.c:1445 [inline]
       __x64_sys_openat+0x139/0x160 fs/open.c:1445
       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

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.2.28/5999:
 #0: ffff88807faca418 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:403
 #1: ffff88804ac82130 (&type->i_mutex_dir_key#9){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
 #1: ffff88804ac82130 (&type->i_mutex_dir_key#9){+.+.}-{3:3}, at: open_last_lookups fs/namei.c:3553 [inline]
 #1: ffff88804ac82130 (&type->i_mutex_dir_key#9){+.+.}-{3:3}, at: path_openat+0x7c6/0x3190 fs/namei.c:3786
 #2: ffff88804ac81e80 (&ni->ni_lock#3/6){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1125 [inline]
 #2: ffff88804ac81e80 (&ni->ni_lock#3/6){+.+.}-{3:3}, at: ntfs_atomic_open+0x1ec/0x520 fs/ntfs3/namei.c:404
 #3: ffff88807fac8270 (&wnd->rw_lock){++++}-{3:3}, at: run_unpack_ex+0x702/0xba0 fs/ntfs3/run.c:1098

stack backtrace:
CPU: 1 PID: 5999 Comm: syz.2.28 Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 <TASK>
 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_read+0x46/0x2e0 kernel/locking/rwsem.c:1520
 run_unpack_ex+0x7e6/0xba0 fs/ntfs3/run.c:1117
 ntfs_read_mft fs/ntfs3/inode.c:401 [inline]
 ntfs_iget5+0x22e3/0x3750 fs/ntfs3/inode.c:533
 dir_search_u+0x1e0/0x2b0 fs/ntfs3/dir.c:264
 ntfs_atomic_open+0x23b/0x520 fs/ntfs3/namei.c:412
 atomic_open fs/namei.c:3351 [inline]
 lookup_open fs/namei.c:3459 [inline]
 open_last_lookups fs/namei.c:3556 [inline]
 path_openat+0xf27/0x3190 fs/namei.c:3786
 do_filp_open+0x1c5/0x3d0 fs/namei.c:3816
 do_sys_openat2+0x12c/0x1c0 fs/open.c:1419
 do_sys_open fs/open.c:1434 [inline]
 __do_sys_openat fs/open.c:1450 [inline]
 __se_sys_openat fs/open.c:1445 [inline]
 __x64_sys_openat+0x139/0x160 fs/open.c:1445
 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
RIP: 0033:0x7f2ef178e9a9
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:00007f2ef25b1038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f2ef19b5fa0 RCX: 00007f2ef178e9a9
RDX: 0000000000143042 RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007f2ef1810d69 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000000a0 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f2ef19b5fa0 R15: 00007ffe9d61b998
 </TASK>