ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512) ====================================================== WARNING: possible circular locking dependency detected 5.15.165-syzkaller #0 Not tainted ------------------------------------------------------ syz.0.1012/7527 is trying to acquire lock: ffff0000e6d69720 (&ni->ni_lock){+.+.}-{3:3}, at: ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:925 but task is already holding lock: ffff0000dd723c00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] ffff0000dd723c00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf8/0x1f8 fs/ntfs3/namei.c:82 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ni->ni_lock/4){+.+.}-{3:3}: __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743 ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] mi_read+0x26c/0x4d8 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:69 [inline] ntfs_iget5+0x358/0x2be0 fs/ntfs3/inode.c:525 ni_update_parent+0x6f0/0xac8 fs/ntfs3/frecord.c:3154 ni_write_inode+0x8a0/0xe38 fs/ntfs3/frecord.c:3252 ntfs3_write_inode+0x70/0x98 fs/ntfs3/inode.c:1037 write_inode fs/fs-writeback.c:1495 [inline] __writeback_single_inode+0x584/0x13a4 fs/fs-writeback.c:1705 writeback_single_inode+0x1c0/0x79c fs/fs-writeback.c:1760 sync_inode_metadata+0xc0/0x124 fs/fs-writeback.c:2820 __generic_file_fsync+0x13c/0x19c fs/libfs.c:1115 generic_file_fsync+0x7c/0xf8 fs/libfs.c:1145 vfs_fsync_range+0x168/0x188 fs/sync.c:188 generic_write_sync include/linux/fs.h:2984 [inline] ntfs_file_write_iter+0x3d4/0x49c fs/ntfs3/file.c:1149 call_write_iter include/linux/fs.h:2172 [inline] new_sync_write fs/read_write.c:507 [inline] vfs_write+0x884/0xb44 fs/read_write.c:594 ksys_pwrite64 fs/read_write.c:701 [inline] __do_sys_pwrite64 fs/read_write.c:711 [inline] __se_sys_pwrite64 fs/read_write.c:708 [inline] __arm64_sys_pwrite64+0x188/0x220 fs/read_write.c:708 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 -> #0 (&ni->ni_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x32d4/0x7638 kernel/locking/lockdep.c:5012 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743 ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:925 ntfs_iget5+0x710/0x2be0 fs/ntfs3/inode.c:532 dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264 ntfs_lookup+0x108/0x1f8 fs/ntfs3/namei.c:83 __lookup_slow+0x250/0x388 fs/namei.c:1663 lookup_slow+0x60/0x84 fs/namei.c:1680 walk_component+0x394/0x4cc fs/namei.c:1976 link_path_walk+0x5a0/0xc38 path_lookupat+0x90/0x3d0 fs/namei.c:2454 filename_lookup+0x1c4/0x4c8 fs/namei.c:2484 user_path_at_empty+0x5c/0x1a4 fs/namei.c:2883 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:490 [inline] __se_sys_chdir fs/open.c:484 [inline] __arm64_sys_chdir+0xc0/0x2d0 fs/open.c:484 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock/4); lock(&ni->ni_lock); lock(&ni->ni_lock/4); lock(&ni->ni_lock); *** DEADLOCK *** 2 locks held by syz.0.1012/7527: #0: ffff0000dd723ea0 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:799 [inline] #0: ffff0000dd723ea0 (&type->i_mutex_dir_key#9){++++}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1679 #1: ffff0000dd723c00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] #1: ffff0000dd723c00 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0xf8/0x1f8 fs/ntfs3/namei.c:82 stack backtrace: CPU: 0 PID: 7527 Comm: syz.0.1012 Not tainted 5.15.165-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 Call trace: dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106 dump_stack+0x1c/0x58 lib/dump_stack.c:113 print_circular_bug+0x150/0x1b8 kernel/locking/lockdep.c:2011 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2133 check_prev_add kernel/locking/lockdep.c:3053 [inline] check_prevs_add kernel/locking/lockdep.c:3172 [inline] validate_chain kernel/locking/lockdep.c:3788 [inline] __lock_acquire+0x32d4/0x7638 kernel/locking/lockdep.c:5012 lock_acquire+0x240/0x77c kernel/locking/lockdep.c:5623 __mutex_lock_common+0x194/0x2154 kernel/locking/mutex.c:596 __mutex_lock kernel/locking/mutex.c:729 [inline] mutex_lock_nested+0xa4/0xf8 kernel/locking/mutex.c:743 ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:925 ntfs_iget5+0x710/0x2be0 fs/ntfs3/inode.c:532 dir_search_u+0x298/0x324 fs/ntfs3/dir.c:264 ntfs_lookup+0x108/0x1f8 fs/ntfs3/namei.c:83 __lookup_slow+0x250/0x388 fs/namei.c:1663 lookup_slow+0x60/0x84 fs/namei.c:1680 walk_component+0x394/0x4cc fs/namei.c:1976 link_path_walk+0x5a0/0xc38 path_lookupat+0x90/0x3d0 fs/namei.c:2454 filename_lookup+0x1c4/0x4c8 fs/namei.c:2484 user_path_at_empty+0x5c/0x1a4 fs/namei.c:2883 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:490 [inline] __se_sys_chdir fs/open.c:484 [inline] __arm64_sys_chdir+0xc0/0x2d0 fs/open.c:484 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 ntfs3: loop0: Mark volume as dirty due to NTFS errors