el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585 ERROR: Out of memory at tomoyo_realpath_from_path. ====================================================== WARNING: possible circular locking dependency detected syzkaller #0 Not tainted ------------------------------------------------------ syz.1.552/6664 is trying to acquire lock: ffff0000f5c05e48 (&sb->s_type->i_mutex_key#10/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000f5c05e48 (&sb->s_type->i_mutex_key#10/1){+.+.}-{3:3}, at: ext4_xattr_inode_create fs/ext4/xattr.c:1462 [inline] ffff0000f5c05e48 (&sb->s_type->i_mutex_key#10/1){+.+.}-{3:3}, at: ext4_xattr_inode_lookup_create+0x1294/0x18f4 fs/ext4/xattr.c:1544 but task is already holding lock: ffff0000e22d8288 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0xfd8/0x150c fs/ext4/inode.c:5612 which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ei->i_data_sem/3){++++}-{3:3}: down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 ext4_update_i_disksize fs/ext4/ext4.h:3396 [inline] ext4_xattr_inode_write fs/ext4/xattr.c:1400 [inline] ext4_xattr_inode_lookup_create+0x11c4/0x18f4 fs/ext4/xattr.c:1550 ext4_xattr_ibody_set+0x1b4/0x5f8 fs/ext4/xattr.c:2209 ext4_xattr_set_handle+0xb2c/0x1344 fs/ext4/xattr.c:2386 ext4_xattr_set+0x1f4/0x2c0 fs/ext4/xattr.c:2500 ext4_xattr_security_set+0x4c/0x64 fs/ext4/xattr_security.c:31 __vfs_setxattr+0x384/0x3a0 fs/xattr.c:182 __vfs_setxattr_noperm+0x120/0x564 fs/xattr.c:216 __vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277 vfs_setxattr+0x158/0x2ac fs/xattr.c:309 do_setxattr fs/xattr.c:594 [inline] setxattr+0x258/0x2d8 fs/xattr.c:617 __do_sys_fsetxattr fs/xattr.c:673 [inline] __se_sys_fsetxattr fs/xattr.c:662 [inline] __arm64_sys_fsetxattr+0x1a8/0x224 fs/xattr.c:662 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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 (&sb->s_type->i_mutex_key#10/1){+.+.}-{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+0x2880/0x6800 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ext4_xattr_inode_create fs/ext4/xattr.c:1462 [inline] ext4_xattr_inode_lookup_create+0x1294/0x18f4 fs/ext4/xattr.c:1544 ext4_xattr_block_set+0x1bc/0x2880 fs/ext4/xattr.c:1864 ext4_xattr_move_to_block fs/ext4/xattr.c:2610 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2685 [inline] ext4_expand_extra_isize_ea+0xe5c/0x17ac fs/ext4/xattr.c:2773 __ext4_expand_extra_isize+0x298/0x358 fs/ext4/inode.c:5984 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6027 [inline] __ext4_mark_inode_dirty+0x3e4/0x784 fs/ext4/inode.c:6105 ext4_setattr+0x102c/0x150c fs/ext4/inode.c:5615 notify_change+0xb0c/0xdcc fs/attr.c:499 do_truncate+0x188/0x20c fs/open.c:65 vfs_truncate+0x23c/0x2b0 fs/open.c:111 do_sys_truncate+0xec/0x1b4 fs/open.c:134 __do_sys_truncate fs/open.c:146 [inline] __se_sys_truncate fs/open.c:144 [inline] __arm64_sys_truncate+0x5c/0x70 fs/open.c:144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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(&ei->i_data_sem/3); lock(&sb->s_type->i_mutex_key#10/1); lock(&ei->i_data_sem/3); lock(&sb->s_type->i_mutex_key#10/1); *** DEADLOCK *** 5 locks held by syz.1.552/6664: #0: ffff0000f3526460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:402 #1: ffff0000e22d8400 (&sb->s_type->i_mutex_key#10){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff0000e22d8400 (&sb->s_type->i_mutex_key#10){++++}-{3:3}, at: do_truncate+0x174/0x20c fs/open.c:63 #2: ffff0000e22d85a0 (mapping.invalidate_lock#2){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline] #2: ffff0000e22d85a0 (mapping.invalidate_lock#2){++++}-{3:3}, at: ext4_setattr+0xbc4/0x150c fs/ext4/inode.c:5572 #3: ffff0000e22d8288 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0xfd8/0x150c fs/ext4/inode.c:5612 #4: ffff0000e22d80c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:165 [inline] #4: ffff0000e22d80c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:6024 [inline] #4: ffff0000e22d80c8 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x37c/0x784 fs/ext4/inode.c:6105 stack backtrace: CPU: 0 PID: 6664 Comm: syz.1.552 Not tainted syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025 Call trace: dump_backtrace+0x1c0/0x1ec arch/arm64/kernel/stacktrace.c:158 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165 __dump_stack+0x30/0x40 lib/dump_stack.c:88 dump_stack_lvl+0xf4/0x15c lib/dump_stack.c:106 dump_stack+0x1c/0x5c lib/dump_stack.c:113 print_circular_bug+0x148/0x1b0 kernel/locking/lockdep.c:2048 check_noncircular+0x264/0x2f8 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+0x2880/0x6800 kernel/locking/lockdep.c:5049 lock_acquire+0x20c/0x63c kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ext4_xattr_inode_create fs/ext4/xattr.c:1462 [inline] ext4_xattr_inode_lookup_create+0x1294/0x18f4 fs/ext4/xattr.c:1544 ext4_xattr_block_set+0x1bc/0x2880 fs/ext4/xattr.c:1864 ext4_xattr_move_to_block fs/ext4/xattr.c:2610 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2685 [inline] ext4_expand_extra_isize_ea+0xe5c/0x17ac fs/ext4/xattr.c:2773 __ext4_expand_extra_isize+0x298/0x358 fs/ext4/inode.c:5984 ext4_try_to_expand_extra_isize fs/ext4/inode.c:6027 [inline] __ext4_mark_inode_dirty+0x3e4/0x784 fs/ext4/inode.c:6105 ext4_setattr+0x102c/0x150c fs/ext4/inode.c:5615 notify_change+0xb0c/0xdcc fs/attr.c:499 do_truncate+0x188/0x20c fs/open.c:65 vfs_truncate+0x23c/0x2b0 fs/open.c:111 do_sys_truncate+0xec/0x1b4 fs/open.c:134 __do_sys_truncate fs/open.c:146 [inline] __se_sys_truncate fs/open.c:144 [inline] __arm64_sys_truncate+0x5c/0x70 fs/open.c:144 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b4 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140 do_el0_svc+0x58/0x130 arch/arm64/kernel/syscall.c:204 el0_svc+0x58/0x128 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