[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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: f45bea23c39c Linux 5.15.162
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16ee4d76980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e4bf7e31dc0c0a74

dashboard link: https://syzkaller.appspot.com/bug?extid=7bcd80feb68037cb0808
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1732c8a5980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16bf37c1980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/4d8c24af3786/disk-f45bea23.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e3446b6ec2ee/vmlinux-f45bea23.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0fb8209336b0/bzImage-f45bea23.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/c404d49bdc07/mount_0.gz

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 loop0): ext4_xattr_inode_create:1422: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3517 at fs/ext4/xattr.c:1423 ext4_xattr_inode_create fs/ext4/xattr.c:1421 [inline]
WARNING: CPU: 1 PID: 3517 at fs/ext4/xattr.c:1423 ext4_xattr_inode_lookup_create fs/ext4/xattr.c:1541 [inline]
WARNING: CPU: 1 PID: 3517 at fs/ext4/xattr.c:1423 ext4_xattr_set_entry+0x2ad3/0x3fb0 fs/ext4/xattr.c:1669
Modules linked in:
CPU: 0 PID: 3517 Comm: syz-executor562 Not tainted 5.15.162-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/07/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 40 52 ff eb 29 e8 c8 40 52 ff 4c 89 ff 48 c7 c6 42 38 18 8c ba 8e 05 00 00 48 c7 c1 20 a0 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 43 52 ff 85
RSP: 0018:ffffc90002f371e0 EFLAGS: 00010246
RAX: c6fb4f0fc93cc300 RBX: 0000000000000000 RCX: c6fb4f0fc93cc300

RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000

RBP: ffffc90002f37470 R08: ffffffff816683dc R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807720a820
R13: 000000000000feeb R14: ffffc90002f37828 R15: ffff8880788fc000
FS: 0000555555e46380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 000055d3c72f4178 CR3: 000000007e3a1000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

ext4_xattr_block_set+0xb10/0x36a0 fs/ext4/xattr.c:1989
ext4_xattr_move_to_block fs/ext4/xattr.c:2616 [inline]
ext4_xattr_make_inode_space fs/ext4/xattr.c:2691 [inline]
ext4_expand_extra_isize_ea+0x10d5/0x1bb0 fs/ext4/xattr.c:2783
__ext4_expand_extra_isize+0x2f7/0x3d0 fs/ext4/inode.c:5840
ext4_try_to_expand_extra_isize fs/ext4/inode.c:5883 [inline]
__ext4_mark_inode_dirty+0x539/0x860 fs/ext4/inode.c:5961
ext4_dirty_inode+0xbf/0x100 fs/ext4/inode.c:5993
__mark_inode_dirty+0x2fd/0xd60 fs/fs-writeback.c:2464
mark_inode_dirty_sync include/linux/fs.h:2467 [inline]
iput+0x1e1/0x8b0 fs/inode.c:1728
__dentry_kill+0x436/0x650 fs/dcache.c:582
shrink_dentry_list+0x398/0x6a0 fs/dcache.c:1177
shrink_dcache_parent+0xc9/0x480
do_one_tree+0x23/0xe0 fs/dcache.c:1658
shrink_dcache_for_umount+0x79/0x120 fs/dcache.c:1675
generic_shutdown_super+0x66/0x2c0 fs/super.c:447
kill_block_super+0x7a/0xe0 fs/super.c:1414
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f99964f9507
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffefc404c28 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000026d9b RCX: 00007f99964f9507
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffefc404ce0
RBP: 00007ffefc404ce0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffefc405d50
R13: 0000555555e476c0 R14: 431bde82d7b634db R15: 00007ffefc405d70
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.