EXT4-fs error (device loop0): ext4_mb_mark_diskspace_used:3806: comm syz-executor.0: Allocating blocks 44-48 which overlap fs metadata
EXT4-fs error (device loop0): ext4_xattr_block_set:2247: inode #12: comm syz-executor.0: bad block 0
============================================
WARNING: possible recursive locking detected
6.4.0-rc2-syzkaller-gf1fcbaa18b28-dirty #0 Not tainted
--------------------------------------------
syz-executor.0/5467 is trying to acquire lock:
ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: ext4_xattr_inode_update_ref+0x87/0x7f0 fs/ext4/xattr.c:1059

but task is already holding lock:
ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: ext4_xattr_inode_update_ref+0x87/0x7f0 fs/ext4/xattr.c:1059

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&ea_inode->i_rwsem#8/1);
  lock(&ea_inode->i_rwsem#8/1);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

4 locks held by syz-executor.0/5467:
 #0: ffff88807a186460 (sb_writers#4){.+.+}-{0:0}, at: path_setxattr+0xb2/0x1c0 fs/xattr.c:670
 #1: ffff8880747ee800 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #1: ffff8880747ee800 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_setxattr+0x120/0x340 fs/xattr.c:321
 #2: ffff8880747ee4c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_write_lock_xattr fs/ext4/xattr.h:155 [inline]
 #2: ffff8880747ee4c8 (&ei->xattr_sem){++++}-{3:3}, at: ext4_xattr_set_handle+0x160/0x1510 fs/ext4/xattr.c:2378
 #3: ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:775 [inline]
 #3: ffff8880747f0400 (&ea_inode->i_rwsem#8/1){+.+.}-{3:3}, at: ext4_xattr_inode_update_ref+0x87/0x7f0 fs/ext4/xattr.c:1059

stack backtrace:
CPU: 0 PID: 5467 Comm: syz-executor.0 Not tainted 6.4.0-rc2-syzkaller-gf1fcbaa18b28-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 print_deadlock_bug kernel/locking/lockdep.c:3001 [inline]
 check_deadlock kernel/locking/lockdep.c:3044 [inline]
 validate_chain kernel/locking/lockdep.c:3829 [inline]
 __lock_acquire+0x13b3/0x5df0 kernel/locking/lockdep.c:5074
 lock_acquire kernel/locking/lockdep.c:5691 [inline]
 lock_acquire+0x1b1/0x520 kernel/locking/lockdep.c:5656
 down_write+0x92/0x200 kernel/locking/rwsem.c:1573
 inode_lock include/linux/fs.h:775 [inline]
 ext4_xattr_inode_update_ref+0x87/0x7f0 fs/ext4/xattr.c:1059
 ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1113 [inline]
 ext4_xattr_block_set+0x24ba/0x3030 fs/ext4/xattr.c:2172
 ext4_xattr_set_handle+0xd8a/0x1510 fs/ext4/xattr.c:2463
 ext4_xattr_set+0x144/0x360 fs/ext4/xattr.c:2565
 __vfs_setxattr+0x173/0x1e0 fs/xattr.c:201
 __vfs_setxattr_noperm+0x129/0x5f0 fs/xattr.c:235
 __vfs_setxattr_locked+0x1d3/0x260 fs/xattr.c:296
 vfs_setxattr+0x143/0x340 fs/xattr.c:322
 do_setxattr+0x147/0x190 fs/xattr.c:630
 setxattr+0x146/0x160 fs/xattr.c:653
 path_setxattr+0x197/0x1c0 fs/xattr.c:672
 __do_sys_setxattr fs/xattr.c:688 [inline]
 __se_sys_setxattr fs/xattr.c:684 [inline]
 __x64_sys_setxattr+0xc4/0x160 fs/xattr.c:684
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f00fb88c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f00fc5b2168 EFLAGS: 00000246 ORIG_RAX: 00000000000000bc
RAX: ffffffffffffffda RBX: 00007f00fb9abf80 RCX: 00007f00fb88c169
RDX: 00000000200005c0 RSI: 0000000020000180 RDI: 0000000020000080
RBP: 00007f00fb8e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000002000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd43d210cf R14: 00007f00fc5b2300 R15: 0000000000022000
 </TASK>