loop3: detected capacity change from 0 to 4096 ====================================================== WARNING: possible circular locking dependency detected 6.1.112-syzkaller #0 Not tainted ------------------------------------------------------ syz.3.366/5447 is trying to acquire lock: ffff0000e16af700 (&ni->ni_lock){+.+.}-{3:3}, at: ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:920 but task is already holding lock: ffff0000e16aefa0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] ffff0000e16aefa0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_rename+0x59c/0xaf8 fs/ntfs3/namei.c:315 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+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] mi_read+0x26c/0x4d8 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:69 [inline] ntfs_iget5+0x360/0x2be8 fs/ntfs3/inode.c:525 ni_update_parent+0x6f0/0xac8 fs/ntfs3/frecord.c:3279 ni_write_inode+0x8a0/0xe3c fs/ntfs3/frecord.c:3377 ntfs3_write_inode+0x70/0x98 fs/ntfs3/inode.c:1031 write_inode fs/fs-writeback.c:1460 [inline] __writeback_single_inode+0x614/0x1770 fs/fs-writeback.c:1677 writeback_single_inode+0x1c0/0x79c fs/fs-writeback.c:1733 sync_inode_metadata+0xd4/0x144 fs/fs-writeback.c:2789 __generic_file_fsync+0x13c/0x19c fs/libfs.c:1143 generic_file_fsync+0x7c/0xf8 fs/libfs.c:1173 vfs_fsync_range+0x168/0x188 fs/sync.c:188 generic_write_sync include/linux/fs.h:2962 [inline] ntfs_file_write_iter+0x49c/0x580 fs/ntfs3/file.c:1169 do_iter_write+0x534/0x964 fs/read_write.c:861 vfs_writev fs/read_write.c:934 [inline] do_pwritev+0x1ec/0x334 fs/read_write.c:1031 __do_sys_pwritev2 fs/read_write.c:1090 [inline] __se_sys_pwritev2 fs/read_write.c:1081 [inline] __arm64_sys_pwritev2+0xd4/0x108 fs/read_write.c:1081 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 -> #0 (&ni->ni_lock){+.+.}-{3:3}: check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:920 ni_remove_name+0x230/0x7a4 fs/ntfs3/frecord.c:2998 ni_rename+0x14c/0x1d8 fs/ntfs3/frecord.c:3150 ntfs_rename+0x5c4/0xaf8 fs/ntfs3/namei.c:318 vfs_rename+0xac8/0xe04 fs/namei.c:4876 do_renameat2+0x9ec/0xe64 fs/namei.c:5029 __do_sys_renameat2 fs/namei.c:5062 [inline] __se_sys_renameat2 fs/namei.c:5059 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5059 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 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 *** 5 locks held by syz.3.366/5447: #0: ffff0000dad1a460 (sb_writers#18){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393 #1: ffff0000e16aa120 (&type->i_mutex_dir_key#14/1){+.+.}-{3:3}, at: do_renameat2+0x538/0xe64 fs/namei.c:4968 #2: ffff0000e16af240 (&sb->s_type->i_mutex_key#28/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline] #2: ffff0000e16af240 (&sb->s_type->i_mutex_key#28/4){+.+.}-{3:3}, at: lock_two_nondirectories+0xc4/0x120 fs/inode.c:1202 #3: ffff0000e16a9e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ni_lock_dir fs/ntfs3/ntfs_fs.h:1106 [inline] #3: ffff0000e16a9e80 (&ni->ni_lock/5){+.+.}-{3:3}, at: ntfs_rename+0x58c/0xaf8 fs/ntfs3/namei.c:314 #4: ffff0000e16aefa0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1101 [inline] #4: ffff0000e16aefa0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_rename+0x59c/0xaf8 fs/ntfs3/namei.c:315 stack backtrace: CPU: 0 PID: 5447 Comm: syz.3.366 Not tainted 6.1.112-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call trace: dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __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:2048 check_noncircular+0x2cc/0x378 kernel/locking/lockdep.c:2170 check_prev_add kernel/locking/lockdep.c:3090 [inline] check_prevs_add kernel/locking/lockdep.c:3209 [inline] validate_chain kernel/locking/lockdep.c:3825 [inline] __lock_acquire+0x3338/0x7680 kernel/locking/lockdep.c:5049 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662 __mutex_lock_common+0x190/0x21a0 kernel/locking/mutex.c:603 __mutex_lock kernel/locking/mutex.c:747 [inline] mutex_lock_nested+0x38/0x44 kernel/locking/mutex.c:799 ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:920 ni_remove_name+0x230/0x7a4 fs/ntfs3/frecord.c:2998 ni_rename+0x14c/0x1d8 fs/ntfs3/frecord.c:3150 ntfs_rename+0x5c4/0xaf8 fs/ntfs3/namei.c:318 vfs_rename+0xac8/0xe04 fs/namei.c:4876 do_renameat2+0x9ec/0xe64 fs/namei.c:5029 __do_sys_renameat2 fs/namei.c:5062 [inline] __se_sys_renameat2 fs/namei.c:5059 [inline] __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5059 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585