From: syzbot <syzbot+c103d3808a0de5faaf80@syzkaller.appspotmail.com>
To: 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,
yebin10@huawei.com
Subject: Re: [syzbot] [xfs?] KASAN: slab-out-of-bounds Read in xfs_getbmap
Date: Mon, 01 May 2023 21:07:19 -0700 [thread overview]
Message-ID: <000000000000569d3405faae13db@google.com> (raw)
In-Reply-To: <000000000000c5beb705faa6577d@google.com>
syzbot has bisected this issue to:
commit 8ee81ed581ff35882b006a5205100db0b57bf070
Author: Ye Bin <yebin10@huawei.com>
Date: Wed Apr 12 05:49:44 2023 +0000
xfs: fix BUG_ON in xfs_getbmap()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1235f544280000
start commit: 58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1135f544280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1635f544280000
kernel config: https://syzkaller.appspot.com/x/.config?x=5eadbf0d3c2ece89
dashboard link: https://syzkaller.appspot.com/bug?extid=c103d3808a0de5faaf80
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12e25f2c280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14945d10280000
Reported-by: syzbot+c103d3808a0de5faaf80@syzkaller.appspotmail.com
Fixes: 8ee81ed581ff ("xfs: fix BUG_ON in xfs_getbmap()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-05-02 4:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 18:53 [syzbot] [xfs?] KASAN: slab-out-of-bounds Read in xfs_getbmap syzbot
2023-05-01 21:26 ` Darrick J. Wong
2023-05-02 11:07 ` Aleksandr Nogikh
2023-05-02 4:07 ` syzbot [this message]
2023-05-02 21:20 ` Darrick J. Wong
2023-05-02 21:20 ` syzbot
2023-05-02 21:24 ` Darrick J. Wong
2023-05-02 21:54 ` syzbot
2023-05-02 22:00 ` Darrick J. Wong
2023-05-03 0:14 ` 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=000000000000569d3405faae13db@google.com \
--to=syzbot+c103d3808a0de5faaf80@syzkaller.appspotmail.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=syzkaller-bugs@googlegroups.com \
--cc=yebin10@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.