[v5.15] WARNING in ext4_xattr_set_entry

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c61bd26ae81a Linux 5.15.160
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1211b972980000
kernel config: https://syzkaller.appspot.com/x/.config?x=235f0e81ca937c17
dashboard link: https://syzkaller.appspot.com/bug?extid=7bcd80feb68037cb0808
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d61a97eef8b9/disk-c61bd26a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ab4908b4b59b/vmlinux-c61bd26a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d818fd46802b/bzImage-c61bd26a.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7bcd80...@syzkaller.appspotmail.com

EXT4-fs warning (device loop3): ext4_xattr_inode_create:1422: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3536 at fs/ext4/xattr.c:1423 ext4_xattr_inode_create fs/ext4/xattr.c:1421 [inline]
WARNING: CPU: 1 PID: 3536 at fs/ext4/xattr.c:1423 ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1541 [inline]
WARNING: CPU: 1 PID: 3536 at fs/ext4/xattr.c:1423 ext4_xattr_set_entry+0x2ad3/0x3fb0 fs/ext4/xattr.c:1669
Modules linked in:
CPU: 1 PID: 3536 Comm: syz-executor.3 Not tainted 5.15.160-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1423 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1541 [inline]
RIP: 0010:ext4_xattr_set_entry+0x2ad3/0x3fb0 fs/ext4/xattr.c:1669
Code: 03 00 00 e8 cf 46 52 ff eb 29 e8 c8 46 52 ff 4c 89 ff 48 c7 c6 82 1c 18 8c ba 8e 05 00 00 48 c7 c1 a0 9f 9d 8a e8 0d 3f fc ff <0f> 0b 48 c7 c3 ea ff ff ff 41 89 dd 31 ff 89 de e8 f8 49 52 ff 85
RSP: 0018:ffffc90002eb71e0 EFLAGS: 00010246
RAX: a2e7ce874259e100 RBX: 0000000000000000 RCX: a2e7ce874259e100
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002eb7470 R08: ffffffff8166860c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88802457b020
R13: 000000000000feeb R14: ffffc90002eb7828 R15: ffff888015fe0000
FS: 0000555556b2b480(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffcb7bbfd8 CR3: 0000000063323000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_xattr_block_set+0xb10/0x3630 fs/ext4/xattr.c:1989


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup