From: syzbot <syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] WARNING in ext4_xattr_inode_update_ref (2)
Date: Thu, 30 Oct 2025 19:15:03 -0700 [thread overview]
Message-ID: <69041ba7.050a0220.3344a1.0452.GAE@google.com> (raw)
In-Reply-To: <20251031015305.1439863-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com
Tested-by: syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com
Tested on:
commit: e53642b8 Merge tag 'v6.18-rc3-smb-server-fixes' of git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c7bfe2580000
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
patch: https://syzkaller.appspot.com/x/patch.diff?x=1473cfe2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-31 2:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 22:34 syzbot
2025-10-31 1:53 ` Lizhi Xu
2025-10-31 2:15 ` syzbot [this message]
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
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=69041ba7.050a0220.3344a1.0452.GAE@google.com \
--to=syzbot+76916a45d2294b551fd9@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®