From: syzbot <syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com>
To: jlbec@evilplan.org, joseph.qi@linux.alibaba.com,
linux-kernel@vger.kernel.org, mark@fasheh.com,
ocfs2-devel@lists.linux.dev, sunjunchao2870@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list
Date: Tue, 10 Dec 2024 03:47:05 -0800 [thread overview]
Message-ID: <67582a39.050a0220.2477f.0063.GAE@google.com> (raw)
In-Reply-To: <a1ef0b7bd9d2491ad346fb2a55b4279c4bd2f1fe.camel@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com
Tested-by: syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com
Tested on:
commit: 50760016 Merge tag 'loongarch-fixes-6.13-1' of git://g..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17037c0f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=50c7a61469ce77e7
dashboard link: https://syzkaller.appspot.com/bug?extid=2313dda4dc4885c93578
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=106c68f8580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-12-10 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 23:04 [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list syzbot
2024-12-10 11:02 ` Edward Adam Davis
2024-12-10 11:28 ` syzbot
2024-12-10 11:23 ` Julian Sun
2024-12-10 11:47 ` syzbot [this message]
2024-12-10 11:27 ` [syzbot] Re: KASAN: use-after-free Read in ocfs2_search_extent_list() syzbot
[not found] <20241210112732.8xyF9%dmantipov@yandex.ru>
2024-12-10 12:06 ` [syzbot] [ocfs2?] KASAN: use-after-free Read in ocfs2_search_extent_list 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=67582a39.050a0220.2477f.0063.GAE@google.com \
--to=syzbot+2313dda4dc4885c93578@syzkaller.appspotmail.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
--cc=sunjunchao2870@gmail.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