From: Dan Carpenter <dan.carpenter@oracle.com>
To: syzbot <syzbot+9c6f0f1f8e32223df9a4@syzkaller.appspotmail.com>
Cc: bridge@lists.linux-foundation.org, davem@davemloft.net,
horatiu.vultur@microchip.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
nikolay@cumulusnetworks.com, roopa@cumulusnetworks.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in br_mrp_parse
Date: Thu, 21 May 2020 17:08:03 +0300 [thread overview]
Message-ID: <20200521140803.GI30374@kadam> (raw)
In-Reply-To: <0000000000007b211005a6187dc9@google.com>
On Wed, May 20, 2020 at 11:23:18AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: dda18a5c selftests/bpf: Convert bpf_iter_test_kern{3, 4}.c..
> git tree: bpf-next
^^^^^^^^
I can figure out what this is from reading Next/Trees but it would be
more useful if it were easier to script.
> console output: https://syzkaller.appspot.com/x/log.txt?x=10c4e63c100000
> kernel config: https://syzkaller.appspot.com/x/.config?x=668983fd3dd1087e
> dashboard link: https://syzkaller.appspot.com/bug?extid=9c6f0f1f8e32223df9a4
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17eaba3c100000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=128598f6100000
>
regards,
dan carpenter
next prev parent reply other threads:[~2020-05-21 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:23 KASAN: slab-out-of-bounds Read in br_mrp_parse syzbot
2020-05-21 14:08 ` Dan Carpenter [this message]
2020-05-21 14:28 ` Dmitry Vyukov
2020-05-21 14:59 ` Dan Carpenter
2020-05-21 15:01 ` Dan Carpenter
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=20200521140803.GI30374@kadam \
--to=dan.carpenter@oracle.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=syzbot+9c6f0f1f8e32223df9a4@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).