From: syzbot <syzbot+fb32afec111a7d61b939@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] KASAN: use-after-free Read in xattr_find_entry (2)
Date: Tue, 24 Feb 2026 02:05:03 -0800 [thread overview]
Message-ID: <699d77cf.a00a0220.121a60.00fa.GAE@google.com> (raw)
In-Reply-To: <20260224085214.19679-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+fb32afec111a7d61b939@syzkaller.appspotmail.com
Tested-by: syzbot+fb32afec111a7d61b939@syzkaller.appspotmail.com
Tested on:
commit: 7dff99b3 Remove WARN_ALL_UNSEEDED_RANDOM kernel config..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f1355a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=93740e6c6567fcec
dashboard link: https://syzkaller.appspot.com/bug?extid=fb32afec111a7d61b939
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=1777b722580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-02-24 10:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260224085214.19679-1-kartikey406@gmail.com>
2026-02-24 10:05 ` syzbot [this message]
[not found] <20260330014309.369720-1-kartikey406@gmail.com>
2026-03-30 2:41 ` [syzbot] [ext4?] KASAN: use-after-free Read in xattr_find_entry (2) syzbot
[not found] <20260327132753.332837-1-kartikey406@gmail.com>
2026-03-27 14:05 ` syzbot
[not found] <20260326145044.29484-1-kartikey406@gmail.com>
2026-03-26 16:59 ` syzbot
[not found] <20260224083610.17722-1-kartikey406@gmail.com>
2026-02-24 9:41 ` syzbot
2026-02-23 0:12 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=699d77cf.a00a0220.121a60.00fa.GAE@google.com \
--to=syzbot+fb32afec111a7d61b939@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox