------------[ cut here ]------------ Looking for class "&ea_inode->i_rwsem" with key ext4_fs_type, but found a different class "&sb->s_type->i_mutex_key" with the same key WARNING: CPU: 1 PID: 5777 at kernel/locking/lockdep.c:933 look_up_lock_class+0xec/0x158 kernel/locking/lockdep.c:930 Modules linked in: CPU: 1 PID: 5777 Comm: syz-executor.5 Not tainted 6.1.72-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : look_up_lock_class+0xec/0x158 kernel/locking/lockdep.c:930 lr : look_up_lock_class+0xec/0x158 kernel/locking/lockdep.c:930 sp : ffff80001e486be0 x29: ffff80001e486be0 x28: dfff800000000000 x27: ffff800008f518d4 x26: ffff8000198507e0 x25: ffff800019850000 x24: 0000000000000000 x23: 0000000000000000 x22: 0000000000000000 x21: ffff800015b91e98 x20: ffff0000e76ac030 x19: ffff80001848bb80 x18: 1ffff00003c90da8 x17: 0000000000000000 x16: ffff80001214b64c x15: 0000000000000000 x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001 x11: 0000000000ff0100 x10: 0000000000000000 x9 : 14afc8815392d800 x8 : 14afc8815392d800 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff80001e4864d8 x4 : ffff800015902b20 x3 : ffff8000085861e8 x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000000 Call trace: look_up_lock_class+0xec/0x158 kernel/locking/lockdep.c:930 register_lock_class+0x90/0x6a8 kernel/locking/lockdep.c:1282 __lock_acquire+0x184/0x7680 kernel/locking/lockdep.c:4928 lock_acquire+0x26c/0x7cc kernel/locking/lockdep.c:5662 down_write+0x5c/0x88 kernel/locking/rwsem.c:1573 inode_lock include/linux/fs.h:756 [inline] ext4_xattr_inode_update_ref+0xac/0x4e0 fs/ext4/xattr.c:993 ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1044 [inline] ext4_xattr_block_set+0x1ed8/0x2c64 fs/ext4/xattr.c:2115 ext4_xattr_set_handle+0xae8/0x1294 fs/ext4/xattr.c:2406 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_setxattr fs/xattr.c:652 [inline] __se_sys_setxattr fs/xattr.c:648 [inline] __arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648 __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 irq event stamp: 259 hardirqs last enabled at (259): [] lookup_bh_lru fs/buffer.c:1291 [inline] hardirqs last enabled at (259): [] __find_get_block+0x1d0/0xeec fs/buffer.c:1303 hardirqs last disabled at (258): [] lookup_bh_lru fs/buffer.c:1272 [inline] hardirqs last disabled at (258): [] __find_get_block+0xa0/0xeec fs/buffer.c:1303 softirqs last enabled at (14): [] local_bh_enable+0x10/0x34 include/linux/bottom_half.h:32 softirqs last disabled at (12): [] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19 ---[ end trace 0000000000000000 ]--- ============================================ WARNING: possible recursive locking detected 6.1.72-syzkaller #0 Tainted: G W -------------------------------------------- syz-executor.5/5777 is trying to acquire lock: ffff0000e76ac030 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] ffff0000e76ac030 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: ext4_xattr_inode_update_ref+0xac/0x4e0 fs/ext4/xattr.c:993 but task is already holding lock: ffff0000e85aa218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] ffff0000e85aa218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:308 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&sb->s_type->i_mutex_key#9); lock(&sb->s_type->i_mutex_key#9); *** DEADLOCK *** May be due to missing lock nesting notation 3 locks held by syz-executor.5/5777: #0: ffff0000ddd3c460 (sb_writers#3){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393 #1: ffff0000e85aa218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline] #1: ffff0000e85aa218 (&sb->s_type->i_mutex_key#9){++++}-{3:3}, at: vfs_setxattr+0x17c/0x344 fs/xattr.c:308 #2: ffff0000e85a9ee0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline] #2: ffff0000e85a9ee0 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x1e0/0x1294 fs/ext4/xattr.c:2321 stack backtrace: CPU: 1 PID: 5777 Comm: syz-executor.5 Tainted: G W 6.1.72-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 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 __lock_acquire+0x6310/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:756 [inline] ext4_xattr_inode_update_ref+0xac/0x4e0 fs/ext4/xattr.c:993 ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1044 [inline] ext4_xattr_block_set+0x1ed8/0x2c64 fs/ext4/xattr.c:2115 ext4_xattr_set_handle+0xae8/0x1294 fs/ext4/xattr.c:2406 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_setxattr fs/xattr.c:652 [inline] __se_sys_setxattr fs/xattr.c:648 [inline] __arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648 __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