loop0: detected capacity change from 0 to 1024 EXT4-fs: Ignoring removed oldalloc option ====================================================== WARNING: possible circular locking dependency detected 6.1.82-syzkaller #0 Not tainted ------------------------------------------------------ syz-executor142/4427 is trying to acquire lock: ffff0000e2181810 (&ea_inode->i_rwsem#9/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] ffff0000e2181810 (&ea_inode->i_rwsem#9/1){+.+.}-{3:3}, at: ext4_xattr_inode_iget+0x34c/0x4e4 fs/ext4/xattr.c:425 but task is already holding lock: ffff0000e21820a0 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x1030/0x14e8 fs/ext4/inode.c:5547 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:3377 [inline] ext4_xattr_inode_write fs/ext4/xattr.c:1397 [inline] ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1545 [inline] ext4_xattr_set_entry+0x26c4/0x3064 fs/ext4/xattr.c:1669 ext4_xattr_ibody_set+0x104/0x328 fs/ext4/xattr.c:2237 ext4_xattr_set_handle+0x9ec/0x1294 fs/ext4/xattr.c:2394 ext4_xattr_set+0x1dc/0x350 fs/ext4/xattr.c:2508 ext4_xattr_trusted_set+0x4c/0x64 fs/ext4/xattr_trusted.c:38 __vfs_setxattr+0x388/0x3a4 fs/xattr.c:182 __vfs_setxattr_noperm+0x110/0x528 fs/xattr.c:216 __vfs_setxattr_locked+0x1ec/0x218 fs/xattr.c:277 vfs_setxattr+0x1a8/0x344 fs/xattr.c:309 do_setxattr fs/xattr.c:594 [inline] setxattr+0x230/0x294 fs/xattr.c:617 path_setxattr+0x17c/0x258 fs/xattr.c:636 __do_sys_lsetxattr fs/xattr.c:659 [inline] __se_sys_lsetxattr fs/xattr.c:655 [inline] __arm64_sys_lsetxattr+0xbc/0xd8 fs/xattr.c:655 __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:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 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 (&ea_inode->i_rwsem#9/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+0x3338/0x7680 kernel/locking/lockdep.c:5049 lock_acquire+0x26c/0x7cc 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_iget+0x34c/0x4e4 fs/ext4/xattr.c:425 ext4_xattr_inode_get+0x148/0x674 fs/ext4/xattr.c:485 ext4_xattr_move_to_block fs/ext4/xattr.c:2590 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2692 [inline] ext4_expand_extra_isize_ea+0xb9c/0x169c fs/ext4/xattr.c:2784 __ext4_expand_extra_isize+0x290/0x348 fs/ext4/inode.c:5919 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5962 [inline] __ext4_mark_inode_dirty+0x484/0x8fc fs/ext4/inode.c:6040 ext4_setattr+0x1094/0x14e8 fs/ext4/inode.c:5550 notify_change+0xb58/0xe1c fs/attr.c:499 do_truncate+0x1c0/0x28c fs/open.c:65 handle_truncate fs/namei.c:3287 [inline] do_open fs/namei.c:3632 [inline] path_openat+0x1fa0/0x2548 fs/namei.c:3785 do_filp_open+0x1bc/0x3cc fs/namei.c:3812 do_sys_openat2+0x128/0x3d8 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __arm64_sys_openat+0x1f0/0x240 fs/open.c:1345 __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:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 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(&ei->i_data_sem/3); lock(&ea_inode->i_rwsem#9/1); lock(&ei->i_data_sem/3); lock(&ea_inode->i_rwsem#9/1); *** DEADLOCK *** 5 locks held by syz-executor142/4427: #0: ffff0000d94f0460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393 #1: ffff0000e2182218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline] #1: ffff0000e2182218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: do_truncate+0x1ac/0x28c fs/open.c:63 #2: ffff0000e21823b8 (mapping.invalidate_lock){++++}-{3:3}, at: filemap_invalidate_lock include/linux/fs.h:803 [inline] #2: ffff0000e21823b8 (mapping.invalidate_lock){++++}-{3:3}, at: ext4_setattr+0xbdc/0x14e8 fs/ext4/inode.c:5507 #3: ffff0000e21820a0 (&ei->i_data_sem/3){++++}-{3:3}, at: ext4_setattr+0x1030/0x14e8 fs/ext4/inode.c:5547 #4: ffff0000e2181ee0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_trylock_xattr fs/ext4/xattr.h:162 [inline] #4: ffff0000e2181ee0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_try_to_expand_extra_isize fs/ext4/inode.c:5959 [inline] #4: ffff0000e2181ee0 (&ei->xattr_sem){++++}-{3:3}, at: __ext4_mark_inode_dirty+0x404/0x8fc fs/ext4/inode.c:6040 stack backtrace: CPU: 0 PID: 4427 Comm: syz-executor142 Not tainted 6.1.82-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/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 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:758 [inline] ext4_xattr_inode_iget+0x34c/0x4e4 fs/ext4/xattr.c:425 ext4_xattr_inode_get+0x148/0x674 fs/ext4/xattr.c:485 ext4_xattr_move_to_block fs/ext4/xattr.c:2590 [inline] ext4_xattr_make_inode_space fs/ext4/xattr.c:2692 [inline] ext4_expand_extra_isize_ea+0xb9c/0x169c fs/ext4/xattr.c:2784 __ext4_expand_extra_isize+0x290/0x348 fs/ext4/inode.c:5919 ext4_try_to_expand_extra_isize fs/ext4/inode.c:5962 [inline] __ext4_mark_inode_dirty+0x484/0x8fc fs/ext4/inode.c:6040 ext4_setattr+0x1094/0x14e8 fs/ext4/inode.c:5550 notify_change+0xb58/0xe1c fs/attr.c:499 do_truncate+0x1c0/0x28c fs/open.c:65 handle_truncate fs/namei.c:3287 [inline] do_open fs/namei.c:3632 [inline] path_openat+0x1fa0/0x2548 fs/namei.c:3785 do_filp_open+0x1bc/0x3cc fs/namei.c:3812 do_sys_openat2+0x128/0x3d8 fs/open.c:1318 do_sys_open fs/open.c:1334 [inline] __do_sys_openat fs/open.c:1350 [inline] __se_sys_openat fs/open.c:1345 [inline] __arm64_sys_openat+0x1f0/0x240 fs/open.c:1345 __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:142 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206 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