ntfs3: loop3: Different NTFS' sector size (4096) and media sector size (512) ntfs3: loop3: Failed to load $Extend. ====================================================== WARNING: possible circular locking dependency detected 5.15.165-syzkaller #0 Not tainted ------------------------------------------------------ syz.3.227/4835 is trying to acquire lock: ffff0000d3d51e80 (&ni->ni_lock){+.+.}-{3:3}, at: ntfs_set_state+0x1a4/0x584 fs/ntfs3/fsntfs.c:925 but task is already holding lock: ffff0000d3d57700 (&ni->ni_lock/4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] ffff0000d3d57700 (&ni->ni_lock/4){+.+.}-{3:3}, at: ntfs_set_ea+0x1b4/0x1228 fs/ntfs3/xattr.c:331 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_sb_inodes+0x94c/0x1654 fs/fs-writeback.c:1930 __writeback_inodes_wb+0x110/0x39c fs/fs-writeback.c:2001 wb_writeback+0x410/0xfc8 fs/fs-writeback.c:2106 wb_check_background_flush fs/fs-writeback.c:2172 [inline] wb_do_writeback fs/fs-writeback.c:2260 [inline] wb_workfn+0xc44/0x1070 fs/fs-writeback.c:2288 process_one_work+0x790/0x11b8 kernel/workqueue.c:2310 worker_thread+0x910/0x1034 kernel/workqueue.c:2457 kthread+0x37c/0x45c kernel/kthread.c:334 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870 -> #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_read_ea+0x210/0x818 fs/ntfs3/xattr.c:177 ntfs_set_ea+0x224/0x1228 fs/ntfs3/xattr.c:342 ntfs_save_wsl_perm+0x100/0x3e8 fs/ntfs3/xattr.c:973 ntfs3_setattr+0x410/0x974 fs/ntfs3/file.c:793 notify_change+0xa34/0xcf8 fs/attr.c:505 chown_common+0x4ac/0x74c fs/open.c:680 vfs_fchown fs/open.c:748 [inline] ksys_fchown+0xe0/0x158 fs/open.c:759 __do_sys_fchown fs/open.c:767 [inline] __se_sys_fchown fs/open.c:765 [inline] __arm64_sys_fchown+0x7c/0x94 fs/open.c:765 __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 *** 3 locks held by syz.3.227/4835: #0: ffff0000d7018460 (sb_writers#12){.+.+}-{0:0}, at: mnt_want_write_file+0x64/0x1e8 fs/namespace.c:421 #1: ffff0000d3d579a0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock include/linux/fs.h:789 [inline] #1: ffff0000d3d579a0 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: chown_common+0x3f8/0x74c fs/open.c:674 #2: ffff0000d3d57700 (&ni->ni_lock /4){+.+.}-{3:3}, at: ni_lock fs/ntfs3/ntfs_fs.h:1100 [inline] /4){+.+.}-{3:3}, at: ntfs_set_ea+0x1b4/0x1228 fs/ntfs3/xattr.c:331 stack backtrace: CPU: 0 PID: 4835 Comm: syz.3.227 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_read_ea+0x210/0x818 fs/ntfs3/xattr.c:177 ntfs_set_ea+0x224/0x1228 fs/ntfs3/xattr.c:342 ntfs_save_wsl_perm+0x100/0x3e8 fs/ntfs3/xattr.c:973 ntfs3_setattr+0x410/0x974 fs/ntfs3/file.c:793 notify_change+0xa34/0xcf8 fs/attr.c:505 chown_common+0x4ac/0x74c fs/open.c:680 vfs_fchown fs/open.c:748 [inline] ksys_fchown+0xe0/0x158 fs/open.c:759 __do_sys_fchown fs/open.c:767 [inline] __se_sys_fchown fs/open.c:765 [inline] __arm64_sys_fchown+0x7c/0x94 fs/open.c:765 __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