From: Aleksandr Nogikh <nogikh@google.com>
To: syzbot <syzbot+7e9494b8b399902e994e@syzkaller.appspotmail.com>
Cc: david@fromorbit.com, dchinner@redhat.com, djwong@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [xfs?] KASAN: use-after-free Read in xfs_btree_lookup_get_block
Date: Mon, 15 May 2023 11:05:10 +0200 [thread overview]
Message-ID: <CANp29Y6G_1hKheTLG9NeSWv4+GYK=zOsUuu_sKCWqEBwGeOYig@mail.gmail.com> (raw)
In-Reply-To: <0000000000001f239205fb969174@google.com>
On Sat, May 13, 2023 at 7:29 PM syzbot
<syzbot+7e9494b8b399902e994e@syzkaller.appspotmail.com> wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit 22ed903eee23a5b174e240f1cdfa9acf393a5210
> Author: Darrick J. Wong <djwong@kernel.org>
> Date: Wed Apr 12 05:49:23 2023 +0000
>
> xfs: verify buffer contents when we skip log replay
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12710f7a280000
> start commit: 1b929c02afd3 Linux 6.2-rc1
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=68e0be42c8ee4bb4
> dashboard link: https://syzkaller.appspot.com/bug?extid=7e9494b8b399902e994e
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172ff2e4480000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11715ea8480000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: xfs: verify buffer contents when we skip log replay
#syz fix: xfs: verify buffer contents when we skip log replay
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
prev parent reply other threads:[~2023-05-15 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000001ca8c205f0f3ee00@google.com>
2023-05-13 17:29 ` [syzbot] [xfs?] KASAN: use-after-free Read in xfs_btree_lookup_get_block syzbot
2023-05-15 9:05 ` Aleksandr Nogikh [this message]
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='CANp29Y6G_1hKheTLG9NeSWv4+GYK=zOsUuu_sKCWqEBwGeOYig@mail.gmail.com' \
--to=nogikh@google.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzbot+7e9494b8b399902e994e@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).