From: syzbot <syzbot+ab0ad25088673470d2d9@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_listxattr
Date: Mon, 10 Nov 2025 21:34:02 -0800 [thread overview]
Message-ID: <6912caca.a70a0220.22f260.0128.GAE@google.com> (raw)
In-Reply-To: <20251111042938.2015551-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ab0ad25088673470d2d9@syzkaller.appspotmail.com
Tested-by: syzbot+ab0ad25088673470d2d9@syzkaller.appspotmail.com
Tested on:
commit: e424ed99 Merge remote-tracking branch 'will/for-next/p..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=16ac6c12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b8b659f0cab27b22
dashboard link: https://syzkaller.appspot.com/bug?extid=ab0ad25088673470d2d9
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=16a1a7cd980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-11 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251111042938.2015551-1-kartikey406@gmail.com>
2025-11-11 5:34 ` syzbot [this message]
[not found] <20251117091717.9916-1-kartikey406@gmail.com>
2025-11-17 11:32 ` [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_listxattr syzbot
[not found] <20251111060615.2022366-1-kartikey406@gmail.com>
2025-11-11 7:09 ` syzbot
[not found] <20251111044000.2016410-1-kartikey406@gmail.com>
2025-11-11 6:02 ` syzbot
[not found] <20251111013052.1801231-1-kartikey406@gmail.com>
2025-11-11 3:17 ` syzbot
2025-11-10 18: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=6912caca.a70a0220.22f260.0128.GAE@google.com \
--to=syzbot+ab0ad25088673470d2d9@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