[v6.1] WARNING in ext4_xattr_inode_lookup_create

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 58485ff1a74f Linux 6.1.141
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1250b20c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c186557a18643a0b
dashboard link: https://syzkaller.appspot.com/bug?extid=acfcc9f1bf6b4476e815
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/467cd5b7e60b/disk-58485ff1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df87a7313b47/vmlinux-58485ff1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/597ae3da22ce/bzImage-58485ff1.xz

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

EXT4-fs warning (device loop1): ext4_xattr_inode_create:1437: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4262 at fs/ext4/xattr.c:1438 ext4_xattr_inode_create fs/ext4/xattr.c:1436 [inline]
WARNING: CPU: 0 PID: 4262 at fs/ext4/xattr.c:1438 ext4_xattr_inode_lookup_create+0xbb7/0x1d10 fs/ext4/xattr.c:1556
Modules linked in:
CPU: 0 PID: 4262 Comm: syz-executor Not tainted 6.1.141-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1438 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create+0xbb7/0x1d10 fs/ext4/xattr.c:1556
Code: 4c 8b 7c 24 20 e9 5d 04 00 00 e8 04 6d 4c ff 48 89 df 48 c7 c6 9a 4e 1d 8c ba 9d 05 00 00 48 c7 c1 00 c0 80 8a e8 09 49 fc ff <0f> 0b 49 c7 c6 ea ff ff ff 48 8b 5c 24 18 43 80 3c 2c 00 74 08 48
RSP: 0018:ffffc900045273e0 EFLAGS: 00010246
RAX: f15815a0469ba500 RBX: ffff8880740be000 RCX: f15815a0469ba500
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc900045275b0 R08: dffffc0000000000 R09: fffff520008a4df5
R10: fffff520008a4df5 R11: 1ffff920008a4df4 R12: 1ffff1100e7957e1
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888073cabee0
FS: 000055556d73b500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000005000 CR3: 000000005b74c000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_xattr_block_set+0x23a/0x32a0 fs/ext4/xattr.c:1876
ext4_xattr_move_to_block fs/ext4/xattr.c:2625 [inline]
ext4_xattr_make_inode_space fs/ext4/xattr.c:2700 [inline]
ext4_expand_extra_isize_ea+0x109b/0x19b0 fs/ext4/xattr.c:2792
__ext4_expand_extra_isize+0x301/0x3e0 fs/ext4/inode.c:5965
ext4_try_to_expand_extra_isize fs/ext4/inode.c:6008 [inline]
__ext4_mark_inode_dirty+0x47f/0x770 fs/ext4/inode.c:6086
ext4_dirty_inode+0xbf/0x100 fs/ext4/inode.c:6118
__mark_inode_dirty+0x322/0xf40 fs/fs-writeback.c:2433
mark_inode_dirty_sync include/linux/fs.h:2551 [inline]
iput+0x1e1/0x980 fs/inode.c:1857
__dentry_kill+0x431/0x650 fs/dcache.c:611
shrink_dentry_list+0x39b/0x6a0 fs/dcache.c:1206
shrink_dcache_parent+0xa8/0x3c0 fs/dcache.c:-1
do_one_tree+0x23/0xe0 fs/dcache.c:1687
shrink_dcache_for_umount+0x65/0x110 fs/dcache.c:1704
generic_shutdown_super+0x63/0x340 fs/super.c:473
kill_block_super+0x7c/0xe0 fs/super.c:1470
deactivate_locked_super+0x93/0xf0 fs/super.c:332
cleanup_mnt+0x463/0x4f0 fs/namespace.c:1182
task_work_run+0x1ca/0x250 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:292 [inline]
syscall_exit_to_user_mode+0x16/0x40 kernel/entry/common.c:303
do_syscall_64+0x58/0xa0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fcd9458fc57
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007fff20e594b8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007fcd94610925 RCX: 00007fcd9458fc57
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff20e59570
RBP: 00007fff20e59570 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff20e5a600
R13: 00007fcd94610925 R14: 0000000000013ea0 R15: 00007fff20e5a640
</TASK>


---
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: 58485ff1a74f Linux 6.1.141
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=162349d4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=c186557a18643a0b
dashboard link: https://syzkaller.appspot.com/bug?extid=acfcc9f1bf6b4476e815
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141e8a82580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121e8a82580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/467cd5b7e60b/disk-58485ff1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/df87a7313b47/vmlinux-58485ff1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/597ae3da22ce/bzImage-58485ff1.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/9c7b56426ac4/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=17ec8a0c580000)

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

EXT4-fs warning (device loop0): ext4_xattr_inode_create:1437: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4248 at fs/ext4/xattr.c:1438 ext4_xattr_inode_create fs/ext4/xattr.c:1436 [inline]
WARNING: CPU: 0 PID: 4248 at fs/ext4/xattr.c:1438 ext4_xattr_inode_lookup_create+0xbb7/0x1d10 fs/ext4/xattr.c:1556
Modules linked in:
CPU: 0 PID: 4248 Comm: syz-executor303 Not tainted 6.1.141-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1438 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create+0xbb7/0x1d10 fs/ext4/xattr.c:1556
Code: 4c 8b 7c 24 20 e9 5d 04 00 00 e8 04 6d 4c ff 48 89 df 48 c7 c6 9a 4e 1d 8c ba 9d 05 00 00 48 c7 c1 00 c0 80 8a e8 09 49 fc ff <0f> 0b 49 c7 c6 ea ff ff ff 48 8b 5c 24 18 43 80 3c 2c 00 74 08 48

RSP: 0018:ffffc90003ac73e0 EFLAGS: 00010246
RAX: 2c35e98da6628f00 RBX: ffff88801db7a000 RCX: 2c35e98da6628f00

RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000

RBP: ffffc90003ac75b0 R08: dffffc0000000000 R09: fffff52000758df5
R10: fffff52000758df5 R11: 1ffff92000758df4 R12: 1ffff1100e74a05b
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888073a502b0
FS: 0000555566a5d380(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 0000555566a666f8 CR3: 000000007770d000 CR4: 00000000003506f0

RIP: 0033:0x7f062cb23547
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:00007ffda9dfaaa8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f062cb23547
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffda9dfab60
RBP: 00007ffda9dfab60 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000202 R12: 00007ffda9dfbbd0
R13: 0000555566a5e6c0 R14: 431bde82d7b634db R15: 00007ffda9dfbbf0
</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.