ntfs3: loop5: Different NTFS sector size (4096) and media sector size (512). ====================================================== WARNING: possible circular locking dependency detected 6.6.0-rc1-next-20230915-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor.5/17197 is trying to acquire lock: ffff88809a5f8100 (&ni->ni_lock#3){+.+.}-{3:3}, at: ntfs_set_state+0x1d2/0x6e0 fs/ntfs3/fsntfs.c:946 but task is already holding lock: ffff88809a5f8fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] ffff88809a5f8fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0x1b8/0x2a0 fs/ntfs3/namei.c:84 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 kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] mi_read+0x462/0x650 fs/ntfs3/record.c:148 ntfs_read_mft fs/ntfs3/inode.c:70 [inline] ntfs_iget5+0x4ee/0x3960 fs/ntfs3/inode.c:532 ni_update_parent fs/ntfs3/frecord.c:3212 [inline] ni_write_inode+0x1503/0x2810 fs/ntfs3/frecord.c:3312 write_inode fs/fs-writeback.c:1456 [inline] __writeback_single_inode+0xa81/0xe70 fs/fs-writeback.c:1668 writeback_single_inode+0x2af/0x590 fs/fs-writeback.c:1724 write_inode_now+0x16e/0x1e0 fs/fs-writeback.c:2766 ntfs_extend+0x2cd/0x520 fs/ntfs3/file.c:355 ntfs_file_write_iter+0x33a/0x1c20 fs/ntfs3/file.c:1076 call_write_iter include/linux/fs.h:1986 [inline] new_sync_write fs/read_write.c:491 [inline] vfs_write+0x650/0xe40 fs/read_write.c:584 ksys_write+0x12f/0x250 fs/read_write.c:637 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd -> #0 (&ni->ni_lock#3){+.+.}-{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:3868 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136 lock_acquire kernel/locking/lockdep.c:5753 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 ntfs_set_state+0x1d2/0x6e0 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x918/0x3960 fs/ntfs3/inode.c:539 dir_search_u+0x162/0x3d0 fs/ntfs3/dir.c:264 ntfs_lookup+0x1c5/0x2a0 fs/ntfs3/namei.c:85 __lookup_slow+0x24d/0x450 fs/namei.c:1693 lookup_slow fs/namei.c:1710 [inline] walk_component+0x349/0x5a0 fs/namei.c:2001 lookup_last fs/namei.c:2458 [inline] path_lookupat+0x17f/0x770 fs/namei.c:2482 filename_lookup+0x1e7/0x5b0 fs/namei.c:2511 user_path_at_empty+0x42/0x60 fs/namei.c:2910 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir fs/open.c:545 [inline] __x64_sys_chdir+0xce/0x270 fs/open.c:545 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ni->ni_lock/4); lock(&ni->ni_lock#3); lock(&ni->ni_lock/4); lock(&ni->ni_lock#3); *** DEADLOCK *** 2 locks held by syz-executor.5/17197: #0: ffff88809a5f9260 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:812 [inline] #0: ffff88809a5f9260 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: lookup_slow fs/namei.c:1709 [inline] #0: ffff88809a5f9260 (&type->i_mutex_dir_key#8){++++}-{3:3}, at: walk_component+0x33b/0x5a0 fs/namei.c:2001 #1: ffff88809a5f8fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1124 [inline] #1: ffff88809a5f8fc0 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_lookup+0x1b8/0x2a0 fs/ntfs3/namei.c:84 stack backtrace: CPU: 0 PID: 17197 Comm: syz-executor.5 Not tainted 6.6.0-rc1-next-20230915-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 check_noncircular+0x311/0x3f0 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:3868 [inline] __lock_acquire+0x2e3d/0x5de0 kernel/locking/lockdep.c:5136 lock_acquire kernel/locking/lockdep.c:5753 [inline] lock_acquire+0x1ae/0x510 kernel/locking/lockdep.c:5718 __mutex_lock_common kernel/locking/mutex.c:603 [inline] __mutex_lock+0x181/0x1340 kernel/locking/mutex.c:747 ntfs_set_state+0x1d2/0x6e0 fs/ntfs3/fsntfs.c:946 ntfs_iget5+0x918/0x3960 fs/ntfs3/inode.c:539 dir_search_u+0x162/0x3d0 fs/ntfs3/dir.c:264 ntfs_lookup+0x1c5/0x2a0 fs/ntfs3/namei.c:85 __lookup_slow+0x24d/0x450 fs/namei.c:1693 lookup_slow fs/namei.c:1710 [inline] walk_component+0x349/0x5a0 fs/namei.c:2001 lookup_last fs/namei.c:2458 [inline] path_lookupat+0x17f/0x770 fs/namei.c:2482 filename_lookup+0x1e7/0x5b0 fs/namei.c:2511 user_path_at_empty+0x42/0x60 fs/namei.c:2910 user_path_at include/linux/namei.h:57 [inline] __do_sys_chdir fs/open.c:551 [inline] __se_sys_chdir fs/open.c:545 [inline] __x64_sys_chdir+0xce/0x270 fs/open.c:545 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f800887cae9 Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f800953c0c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000050 RAX: ffffffffffffffda RBX: 00007f800899bf80 RCX: 00007f800887cae9 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000020000040 RBP: 00007f80088c847a R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 000000000000000b R14: 00007f800899bf80 R15: 00007ffc57f9c778 ntfs3: loop5: Mark volume as dirty due to NTFS errors