* [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
@ 2025-10-30 22:34 syzbot
2025-10-31 1:53 ` Lizhi Xu
` (3 more replies)
0 siblings, 4 replies; 9+ messages in thread
From: syzbot @ 2025-10-30 22:34 UTC (permalink / raw)
To: adilger.kernel, linux-ext4, linux-kernel, syzkaller-bugs, tytso
Hello,
syzbot found the following issue on:
HEAD commit: e53642b87a4f Merge tag 'v6.18-rc3-smb-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=150aa32f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=929790bc044e87d7
dashboard link: https://syzkaller.appspot.com/bug?extid=76916a45d2294b551fd9
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=101f5f34580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=121dbe7c580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-e53642b8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/bb13d82854da/vmlinux-e53642b8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f3a72d29f243/bzImage-e53642b8.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fb4c6b817064/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16191fe2580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com
EXT4-fs warning (device loop0): ext4_xattr_inode_get:546: inode #11: comm syz.0.17: ea_inode file size=0 entry size=6
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2853: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 i_nlink=2
WARNING: CPU: 0 PID: 5496 at fs/ext4/xattr.c:1058 ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056
Modules linked in:
CPU: 0 UID: 0 PID: 5496 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056
Code: 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 0f 85 80 00 00 00 41 8b 17 48 c7 c7 80 1f 80 8b 4c 89 e6 e8 a7 1b f8 fe 90 <0f> 0b 90 90 4c 8b 6c 24 28 e9 59 fe ff ff e8 f3 0b bd 08 44 89 f9
RSP: 0018:ffffc90002847240 EFLAGS: 00010246
RAX: 96417f00249f1400 RBX: 0000000000000001 RCX: ffff88801f648000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: ffffc90002847330 R08: ffff88801fe24293 R09: 1ffff11003fc4852
R10: dffffc0000000000 R11: ffffed1003fc4853 R12: 000000000000000b
R13: ffff8880121df630 R14: 1ffff1100243beb4 R15: ffff8880121df5a0
FS: 000055557b2d3500(0000) GS:ffff88808d733000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd0e033d000 CR3: 000000004bac3000 CR4: 0000000000352ef0
Call Trace:
<TASK>
ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1081 [inline]
ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1223
ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2947
ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271
evict+0x504/0x9c0 fs/inode.c:810
ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:470
__ext4_fill_super fs/ext4/super.c:5617 [inline]
ext4_fill_super+0x5920/0x61e0 fs/ext4/super.c:5736
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9e5239076a
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:00007ffd45601928 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffd456019b0 RCX: 00007f9e5239076a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007ffd45601970
RBP: 0000200000000180 R08: 00007ffd456019b0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007ffd45601970 R14: 000000000000046c R15: 0000200000000680
</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 syzkaller@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 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.
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
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
2025-10-30 22:34 [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
@ 2025-10-31 1:53 ` Lizhi Xu
2025-10-31 2:15 ` syzbot
2025-11-03 7:46 ` Lizhi Xu
` (2 subsequent siblings)
3 siblings, 1 reply; 9+ messages in thread
From: Lizhi Xu @ 2025-10-31 1:53 UTC (permalink / raw)
To: syzbot+76916a45d2294b551fd9; +Cc: linux-kernel, syzkaller-bugs
#syz test
diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
index ce7253b3f549..8babe8c344fe 100644
--- a/fs/ext4/xattr.c
+++ b/fs/ext4/xattr.c
@@ -1192,6 +1192,14 @@ ext4_xattr_inode_dec_ref_all(handle_t *handle, struct inode *parent,
if (err)
continue;
+ size_t size = le32_to_cpu(entry->e_value_size);
+ if (i_size_read(ea_inode) != size) {
+ ext4_warning_inode(ea_inode,
+ "ea_inode file size=%llu entry size=%zu",
+ i_size_read(ea_inode), size);
+ iput(ea_inode);
+ continue;
+ }
err = ext4_expand_inode_array(ea_inode_array, ea_inode);
if (err) {
ext4_warning_inode(ea_inode,
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
2025-10-30 22:34 [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
2025-10-31 1:53 ` Lizhi Xu
@ 2025-11-03 7:46 ` Lizhi Xu
2025-11-03 8:15 ` syzbot
2025-11-03 8:23 ` Forwarded: " syzbot
2025-11-06 7:26 ` Forwarded: Re: [syzbot] [sound?] [usb?] KASAN: slab-out-of-bounds Write in copy_to_urb syzbot
3 siblings, 1 reply; 9+ messages in thread
From: Lizhi Xu @ 2025-11-03 7:46 UTC (permalink / raw)
To: syzbot+76916a45d2294b551fd9; +Cc: linux-kernel, syzkaller-bugs
#syz test
diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
index ce7253b3f549..b7860b96e8bb 100644
--- a/fs/ext4/xattr.c
+++ b/fs/ext4/xattr.c
@@ -1041,6 +1041,13 @@ static int ext4_xattr_inode_update_ref(handle_t *handle, struct inode *ea_inode,
goto out;
}
ref_count += ref_change;
+ if (overflows_type(ref_count, u64)) {
+ ext4_error_inode(ea_inode, __func__, __LINE__, 0,
+ "EA inode %lu ref overflows: ref_count=%lld ref_change=%d",
+ ea_inode->i_ino, ref_count, ref_change);
+ ret = -EFSCORRUPTED;
+ goto out;
+ }
ext4_xattr_inode_set_ref(ea_inode, ref_count);
if (ref_change > 0) {
^ permalink raw reply related [flat|nested] 9+ messages in thread* Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
2025-11-03 7:46 ` Lizhi Xu
@ 2025-11-03 8:15 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2025-11-03 8:15 UTC (permalink / raw)
To: linux-kernel, lizhi.xu, syzkaller-bugs
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 warning (device loop0): ext4_xattr_inode_get:546: inode #11: comm syz.0.17: ea_inode file size=0 entry size=6
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2860: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 i_nlink=2
WARNING: CPU: 0 PID: 6571 at fs/ext4/xattr.c:1065 ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1063
Modules linked in:
CPU: 0 UID: 0 PID: 6571 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1063
Code: 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 0f 85 80 00 00 00 41 8b 17 48 c7 c7 00 9b ff 8a 4c 89 e6 e8 97 9a 03 ff 90 <0f> 0b 90 90 4c 8b 6c 24 28 e9 59 fe ff ff e8 33 f6 40 08 44 89 f9
RSP: 0018:ffffc90004067240 EFLAGS: 00010246
RAX: 07a0f86583ac9f00 RBX: 0000000000000001 RCX: ffff888026411e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90004067330 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101710487b R12: 000000000000000b
R13: ffff8880412ca7d8 R14: 1ffff110082594e1 R15: ffff8880412ca708
FS: 00007f06408966c0(0000) GS:ffff888126df9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f186f706000 CR3: 0000000053790000 CR4: 00000000003526f0
Call Trace:
<TASK>
ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1088 [inline]
ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1230
ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2954
ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271
evict+0x504/0x9c0 fs/inode.c:810
ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:470
__ext4_fill_super fs/ext4/super.c:5617 [inline]
ext4_fill_super+0x593b/0x61f0 fs/ext4/super.c:5736
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f064123076a
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:00007f0640895e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f0640895ef0 RCX: 00007f064123076a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007f0640895eb0
RBP: 0000200000000180 R08: 00007f0640895ef0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f0640895eb0 R14: 000000000000046c R15: 0000200000000680
</TASK>
Tested on:
commit: 6146a0f1 Linux 6.18-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10037932580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=76916a45d2294b551fd9
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=11386012580000
^ permalink raw reply [flat|nested] 9+ messages in thread
* Forwarded: Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
2025-10-30 22:34 [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
2025-10-31 1:53 ` Lizhi Xu
2025-11-03 7:46 ` Lizhi Xu
@ 2025-11-03 8:23 ` syzbot
2025-11-06 7:26 ` Forwarded: Re: [syzbot] [sound?] [usb?] KASAN: slab-out-of-bounds Write in copy_to_urb syzbot
3 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2025-11-03 8:23 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
Author: lizhi.xu@windriver.com
#syz test
diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
index ce7253b3f549..5f535d45111b 100644
--- a/fs/ext4/xattr.c
+++ b/fs/ext4/xattr.c
@@ -1040,6 +1040,13 @@ static int ext4_xattr_inode_update_ref(handle_t *handle, struct inode *ea_inode,
ret = -EFSCORRUPTED;
goto out;
}
+ if (overflows_type(ref_count + ref_change, u64)) {
+ ext4_error_inode(ea_inode, __func__, __LINE__, 0,
+ "EA inode %lu ref overflows: ref_count=%lld ref_change=%d",
+ ea_inode->i_ino, ref_count, ref_change);
+ ret = -EFSCORRUPTED;
+ goto out;
+ }
ref_count += ref_change;
ext4_xattr_inode_set_ref(ea_inode, ref_count);
^ permalink raw reply related [flat|nested] 9+ messages in thread* Forwarded: Re: [syzbot] [sound?] [usb?] KASAN: slab-out-of-bounds Write in copy_to_urb
2025-10-30 22:34 [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
` (2 preceding siblings ...)
2025-11-03 8:23 ` Forwarded: " syzbot
@ 2025-11-06 7:26 ` syzbot
3 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2025-11-06 7:26 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: [syzbot] [sound?] [usb?] KASAN: slab-out-of-bounds Write in copy_to_urb
Author: lizhi.xu@windriver.com
#syz test
diff --git a/sound/usb/pcm.c b/sound/usb/pcm.c
index 54d01dfd820f..a4c0ea685b8a 100644
--- a/sound/usb/pcm.c
+++ b/sound/usb/pcm.c
@@ -1606,6 +1606,9 @@ static int prepare_playback_urb(struct snd_usb_substream *subs,
subs->cur_audiofmt->dsd_bitrev)) {
fill_playback_urb_dsd_bitrev(subs, urb, bytes);
} else {
+ if (bytes > ctx->buffer_size)
+ return -EPIPE;
+
/* usual PCM */
if (!subs->tx_length_quirk)
copy_to_urb(subs, urb, 0, stride, bytes);
^ permalink raw reply related [flat|nested] 9+ messages in thread
[parent not found: <20251103082353.294139-1-lizhi.xu@windriver.com>]
* Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
[not found] <20251103082353.294139-1-lizhi.xu@windriver.com>
@ 2025-11-03 8:45 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2025-11-03 8:45 UTC (permalink / raw)
To: linux-kernel, lizhi.xu, syzkaller-bugs
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 warning (device loop0): ext4_xattr_inode_get:546: inode #11: comm syz.0.17: ea_inode file size=0 entry size=6
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2860: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 i_nlink=2
WARNING: CPU: 0 PID: 6567 at fs/ext4/xattr.c:1065 ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1063
Modules linked in:
CPU: 0 UID: 0 PID: 6567 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1063
Code: 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 0f 85 80 00 00 00 41 8b 17 48 c7 c7 00 9b ff 8a 4c 89 e6 e8 97 9a 03 ff 90 <0f> 0b 90 90 4c 8b 6c 24 28 e9 59 fe ff ff e8 33 f6 40 08 44 89 f9
RSP: 0018:ffffc900015af240 EFLAGS: 00010246
RAX: eaaccfe6fa323400 RBX: 0000000000000001 RCX: ffff88803a701e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900015af330 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101710487b R12: 000000000000000b
R13: ffff8880411b1028 R14: 1ffff110082361eb R15: ffff8880411b0f58
FS: 00007f83656ee6c0(0000) GS:ffff888126df9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3c433ce000 CR3: 000000002b77c000 CR4: 00000000003526f0
Call Trace:
<TASK>
ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1088 [inline]
ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1230
ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2954
ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271
evict+0x504/0x9c0 fs/inode.c:810
ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:470
__ext4_fill_super fs/ext4/super.c:5617 [inline]
ext4_fill_super+0x593b/0x61f0 fs/ext4/super.c:5736
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f836608076a
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:00007f83656ede68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f83656edef0 RCX: 00007f836608076a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007f83656edeb0
RBP: 0000200000000180 R08: 00007f83656edef0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f83656edeb0 R14: 000000000000046c R15: 0000200000000680
</TASK>
Tested on:
commit: 6146a0f1 Linux 6.18-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10062292580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=76916a45d2294b551fd9
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=14c0c532580000
^ permalink raw reply [flat|nested] 9+ messages in thread
[parent not found: <20251106072648.2607754-1-lizhi.xu@windriver.com>]
* Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
[not found] <20251106072648.2607754-1-lizhi.xu@windriver.com>
@ 2025-11-06 7:47 ` syzbot
0 siblings, 0 replies; 9+ messages in thread
From: syzbot @ 2025-11-06 7:47 UTC (permalink / raw)
To: linux-kernel, lizhi.xu, syzkaller-bugs
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 warning (device loop0): ext4_xattr_inode_get:546: inode #11: comm syz.0.17: ea_inode file size=0 entry size=6
EXT4-fs warning (device loop0): ext4_expand_extra_isize_ea:2853: Unable to expand inode 15. Delete some EAs or run e2fsck.
------------[ cut here ]------------
EA inode 11 i_nlink=2
WARNING: CPU: 0 PID: 6694 at fs/ext4/xattr.c:1058 ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056
Modules linked in:
CPU: 0 UID: 0 PID: 6694 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:ext4_xattr_inode_update_ref+0x51a/0x5b0 fs/ext4/xattr.c:1056
Code: 48 b8 00 00 00 00 00 fc ff df 41 0f b6 04 06 84 c0 0f 85 80 00 00 00 41 8b 17 48 c7 c7 00 9b ff 8a 4c 89 e6 e8 97 9a 03 ff 90 <0f> 0b 90 90 4c 8b 6c 24 28 e9 59 fe ff ff e8 33 f6 40 08 44 89 f9
RSP: 0018:ffffc90003a4f240 EFLAGS: 00010246
RAX: 9784c33726edfd00 RBX: 0000000000000001 RCX: ffff888020bb8000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90003a4f330 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed101710487b R12: 000000000000000b
R13: ffff888059283f88 R14: 1ffff1100b2507d7 R15: ffff888059283eb8
FS: 00007f0477f2e6c0(0000) GS:ffff888126df9000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f7f5e2ee440 CR3: 0000000028ad6000 CR4: 00000000003526f0
Call Trace:
<TASK>
ext4_xattr_inode_dec_ref fs/ext4/xattr.c:1081 [inline]
ext4_xattr_inode_dec_ref_all+0x867/0xda0 fs/ext4/xattr.c:1223
ext4_xattr_delete_inode+0xa4c/0xc10 fs/ext4/xattr.c:2947
ext4_evict_inode+0xac9/0xee0 fs/ext4/inode.c:271
evict+0x504/0x9c0 fs/inode.c:810
ext4_orphan_cleanup+0xc20/0x1460 fs/ext4/orphan.c:470
__ext4_fill_super fs/ext4/super.c:5617 [inline]
ext4_fill_super+0x593b/0x61f0 fs/ext4/super.c:5736
get_tree_bdev_flags+0x40e/0x4d0 fs/super.c:1691
vfs_get_tree+0x92/0x2b0 fs/super.c:1751
fc_mount fs/namespace.c:1208 [inline]
do_new_mount_fc fs/namespace.c:3651 [inline]
do_new_mount+0x302/0xa10 fs/namespace.c:3727
do_mount fs/namespace.c:4050 [inline]
__do_sys_mount fs/namespace.c:4238 [inline]
__se_sys_mount+0x313/0x410 fs/namespace.c:4215
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xfa/0xfa0 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f04788c076a
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:00007f0477f2de68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f0477f2def0 RCX: 00007f04788c076a
RDX: 0000200000000180 RSI: 00002000000001c0 RDI: 00007f0477f2deb0
RBP: 0000200000000180 R08: 00007f0477f2def0 R09: 0000000000800700
R10: 0000000000800700 R11: 0000000000000246 R12: 00002000000001c0
R13: 00007f0477f2deb0 R14: 000000000000046c R15: 0000200000000680
</TASK>
Tested on:
commit: dc77806c Merge tag 'rust-fixes-6.18' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b64a92580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=76916a45d2294b551fd9
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=1731617c580000
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2025-11-06 7:47 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-10-30 22:34 [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
2025-10-31 1:53 ` Lizhi Xu
2025-10-31 2:15 ` syzbot
2025-11-03 7:46 ` Lizhi Xu
2025-11-03 8:15 ` syzbot
2025-11-03 8:23 ` Forwarded: " syzbot
2025-11-06 7:26 ` Forwarded: Re: [syzbot] [sound?] [usb?] KASAN: slab-out-of-bounds Write in copy_to_urb syzbot
[not found] <20251103082353.294139-1-lizhi.xu@windriver.com>
2025-11-03 8:45 ` [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2) syzbot
[not found] <20251106072648.2607754-1-lizhi.xu@windriver.com>
2025-11-06 7:47 ` syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox