From: Dmitry Vyukov <dvyukov@google.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: syzbot <syzbot+9c6f0f1f8e32223df9a4@syzkaller.appspotmail.com>,
bridge@lists.linux-foundation.org,
David Miller <davem@davemloft.net>,
horatiu.vultur@microchip.com, kuba@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: KASAN: slab-out-of-bounds Read in br_mrp_parse
Date: Thu, 21 May 2020 16:28:05 +0200 [thread overview]
Message-ID: <CACT4Y+bzz-h5vNGH0rDMUiuGZVX01oXawXAPbjtnNHb1KVWSvg@mail.gmail.com> (raw)
In-Reply-To: <20200521140803.GI30374@kadam>
On Thu, May 21, 2020 at 4:08 PM Dan Carpenter <dan.carpenter@oracle.com> wrote:
>
> 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.
Hi Dan,
Is there a canonical way to refer to a particular branch of a particular tree?
From what I observed on mailing lists people seem to say "linux-next"
or "upstream tree" and that seems to mean specific things that
everybody understands.
What do you want to script? Note syzbot is not promising a specific
stable API wrt these plain text emails. These are flattened into text
format for human consumption and sent over unreliable media.
> > 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
>
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/20200521140803.GI30374%40kadam.
next prev parent reply other threads:[~2020-05-21 14:28 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
2020-05-21 14:28 ` Dmitry Vyukov [this message]
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=CACT4Y+bzz-h5vNGH0rDMUiuGZVX01oXawXAPbjtnNHb1KVWSvg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=bridge@lists.linux-foundation.org \
--cc=dan.carpenter@oracle.com \
--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 \
--cc=syzkaller@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).