From: syzbot <syzbot+4c9d23743a2409b80293@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] WARNING in ext4_xattr_block_set (3)
Date: Tue, 23 Sep 2025 01:55:02 -0700 [thread overview]
Message-ID: <68d26066.050a0220.139b6.0025.GAE@google.com> (raw)
In-Reply-To: <20250923083522.1086124-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in ext4_xattr_inode_update_ref
loop0: detected capacity change from 0 to 512
EXT4-fs (loop0): orphan cleanup on readonly fs
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2851: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 i_nlink=2
WARNING: CPU: 1 PID: 6503 at fs/ext4/xattr.c:1053 ext4_xattr_inode_update_ref+0x534/0x5d0 fs/ext4/xattr.c:1051
Modules linked in:
CPU: 1 UID: 0 PID: 6503 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
RIP: 0010:ext4_xattr_inode_update_ref+0x534/0x5d0 fs/ext4/xattr.c:1051
Code: 00 00 00 00 00 fc ff df 41 0f b6 44 05 00 84 c0 0f 85 86 00 00 00 41 8b 14 24 48 c7 c7 e0 70 1f 8b 4c 89 fe e8 ed 87 07 ff 90 <0f> 0b 90 90 48 bb 00 00 00 00 00 fc ff df e9 bb fd ff ff e8 74 59
RSP: 0018:ffffc900042af2e0 EFLAGS: 00010246
RAX: ce552e21466e5d00 RBX: dffffc0000000000 RCX: ffff88802f2e8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900042af3d0 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed1017124863 R12: ffff888057ec8f58
R13: 1ffff1100afd91eb R14: 00000000ffffffff R15: 000000000000000b
FS: 00007f61d52b66c0(0000) GS:ffff8881269bc000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0c2b6a1000 CR3: 0000000025d4e000 CR4: 00000000003526f0
Call Trace:
<TASK>
ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1076 [inline]
ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1218
ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2945
ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271
evict+0x501/0x9c0 fs/inode.c:810
ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:474
__ext4_fill_super fs/ext4/super.c:5609 [inline]
ext4_fill_super+0x57fa/0x60b0 fs/ext4/super.c:5728
get_tree_bdev_flags+0x40b/0x4d0 fs/super.c:1692
vfs_get_tree+0x8f/0x2b0 fs/super.c:1815
do_new_mount+0x2a2/0x9e0 fs/namespace.c:3808
do_mount fs/namespace.c:4136 [inline]
__do_sys_mount fs/namespace.c:4347 [inline]
__se_sys_mount+0x317/0x410 fs/namespace.c:4324
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f61d5c5066a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f61d52b5e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f61d52b5ef0 RCX: 00007f61d5c5066a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007f61d52b5eb0
RBP: 0000200000000180 R08: 00007f61d52b5ef0 R09: 000000000080078b
R10: 000000000080078b R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f61d52b5eb0 R14: 0000000000000473 R15: 0000200000000680
</TASK>
Tested on:
commit: cec1e6e5 Merge tag 'sched_ext-for-6.17-rc7-fixes' of g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16fd04e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=4c9d23743a2409b80293
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=132d04e2580000
next parent reply other threads:[~2025-09-23 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250923083522.1086124-1-kartikey406@gmail.com>
2025-09-23 8:55 ` syzbot [this message]
[not found] <20250923061138.1081531-1-kartikey406@gmail.com>
2025-09-23 6:29 ` [syzbot] [ext4?] WARNING in ext4_xattr_block_set (3) syzbot
2025-09-23 5:02 [PATCH] ext4: skip inode expansion on readonly filesystems Deepanshu Kartikey
2025-09-23 5:43 ` [syzbot] [ext4?] WARNING in ext4_xattr_block_set (3) syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-09-23 2:31 [PATCH] ext4: skip inode expansion on readonly filesystems Deepanshu Kartikey
2025-09-23 3:22 ` [syzbot] [ext4?] WARNING in ext4_xattr_block_set (3) syzbot
2025-09-16 20:09 syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68d26066.050a0220.139b6.0025.GAE@google.com \
--to=syzbot+4c9d23743a2409b80293@syzkaller.appspotmail.com \
--cc=kartikey406@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.