[v6.6] WARNING in ext4_xattr_inode_lookup_create

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=137a1cf0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=116ea5ac2d7f27405104
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz

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

EXT4-fs warning (device loop3): ext4_xattr_inode_create:1486: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5789 at fs/ext4/xattr.c:1487 ext4_xattr_inode_create fs/ext4/xattr.c:1485 [inline]
WARNING: CPU: 0 PID: 5789 at fs/ext4/xattr.c:1487 ext4_xattr_inode_lookup_create+0x5be/0x1d80 fs/ext4/xattr.c:1605
Modules linked in:
CPU: 0 PID: 5789 Comm: syz-executor Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1487 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create+0x5be/0x1d80 fs/ext4/xattr.c:1605
Code: 4c 8b 7c 24 10 e9 12 0a 00 00 e8 2d ea 43 ff 48 89 df 48 c7 c6 bb df 5b 8c ba ce 05 00 00 48 c7 c1 60 d0 be 8a e8 52 56 fc ff <0f> 0b 49 c7 c6 ea ff ff ff 48 8b 5c 24 08 e9 fe 09 00 00 48 8d 78
RSP: 0018:ffffc90002e473e0 EFLAGS: 00010246
RAX: 810f8eb134350e00 RBX: ffff888026830000 RCX: 810f8eb134350e00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90002e475b0 R08: ffffc90002e46fa7 R09: 1ffff920005c8df4
R10: dffffc0000000000 R11: fffff520005c8df5 R12: ffff88805cd15ce8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff88805cd15cb0
FS: 000055556a011500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055556a02c5c8 CR3: 0000000060849000 CR4: 00000000003526f0
DR0: 0000000000000006 DR1: 0000000000000008 DR2: 0000000000000000
DR3: 0000000000000008 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_xattr_block_set+0x23e/0x32a0 fs/ext4/xattr.c:1925
ext4_xattr_move_to_block fs/ext4/xattr.c:2674 [inline]
ext4_xattr_make_inode_space fs/ext4/xattr.c:2749 [inline]
ext4_expand_extra_isize_ea+0x10ea/0x19e0 fs/ext4/xattr.c:2841
__ext4_expand_extra_isize+0x306/0x400 fs/ext4/inode.c:5953
ext4_try_to_expand_extra_isize fs/ext4/inode.c:5996 [inline]
__ext4_mark_inode_dirty+0x45d/0x6e0 fs/ext4/inode.c:6074
ext4_dirty_inode+0xcb/0x110 fs/ext4/inode.c:6106
__mark_inode_dirty+0x2b4/0xc80 fs/fs-writeback.c:2455
mark_inode_dirty_sync include/linux/fs.h:2309 [inline]
iput+0x1cc/0x920 fs/inode.c:1843
__dentry_kill+0x431/0x650 fs/dcache.c:611
shrink_dentry_list+0x39f/0x6a0 fs/dcache.c:1206
shrink_dcache_parent+0xac/0x3c0 fs/dcache.c:-1
do_one_tree+0x23/0xe0 fs/dcache.c:1686
shrink_dcache_for_umount+0x69/0x110 fs/dcache.c:1703
generic_shutdown_super+0x67/0x2b0 fs/super.c:665
kill_block_super+0x44/0x90 fs/super.c:1660
ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7396
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1250
task_work_run+0x1ce/0x250 kernel/task_work.c:239
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:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7997f8fe97
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:00007ffd5add2ad8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f7998011bdd RCX: 00007f7997f8fe97
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffd5add2b90
RBP: 00007ffd5add2b90 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffd5add3c20
R13: 00007f7998011bdd R14: 0000000000028408 R15: 00007ffd5add3c60
</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: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y

console output: https://syzkaller.appspot.com/x/log.txt?x=15e71cf0580000

kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=116ea5ac2d7f27405104
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e5d2a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15afd9bc580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/f9d22ecdafe4/mount_0.gz
fsck result: OK (log: https://syzkaller.appspot.com/x/fsck.log?x=1765d2a2580000)

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

EXT4-fs warning (device loop0): ext4_xattr_inode_create:1486: refuse to create EA inode when umounting
------------[ cut here ]------------
WARNING: CPU: 0 PID: 5895 at fs/ext4/xattr.c:1487 ext4_xattr_inode_create fs/ext4/xattr.c:1485 [inline]
WARNING: CPU: 0 PID: 5895 at fs/ext4/xattr.c:1487 ext4_xattr_inode_lookup_create+0x5be/0x1d80 fs/ext4/xattr.c:1605
Modules linked in:
CPU: 0 PID: 5895 Comm: syz-executor Not tainted 6.6.100-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:ext4_xattr_inode_create fs/ext4/xattr.c:1487 [inline]
RIP: 0010:ext4_xattr_inode_lookup_create+0x5be/0x1d80 fs/ext4/xattr.c:1605
Code: 4c 8b 7c 24 10 e9 12 0a 00 00 e8 2d ea 43 ff 48 89 df 48 c7 c6 bb df 5b 8c ba ce 05 00 00 48 c7 c1 60 d0 be 8a e8 52 56 fc ff <0f> 0b 49 c7 c6 ea ff ff ff 48 8b 5c 24 08 e9 fe 09 00 00 48 8d 78

RSP: 0018:ffffc900033073e0 EFLAGS: 00010246
RAX: 1861383e2d852400 RBX: ffff88802d34c000 RCX: 1861383e2d852400

RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000

RBP: ffffc900033075b0 R08: ffffc90003306fa7 R09: 1ffff92000660df4
R10: dffffc0000000000 R11: fffff52000660df5 R12: ffff888072e852e8
R13: dffffc0000000000 R14: 0000000000000000 R15: ffff888072e852b0
FS: 000055558a37f500(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 00007fff5c99dd38 CR3: 000000007f74a000 CR4: 00000000003506f0

RIP: 0033:0x7f9bd338fe97

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:00007fff5c99e4e8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f9bd3411bdd RCX: 00007f9bd338fe97
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007fff5c99e5a0
RBP: 00007fff5c99e5a0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fff5c99f630
R13: 00007f9bd3411bdd R14: 0000000000019ce5 R15: 00007fff5c99f670
</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.