From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: syzbot <syzbot+017b1f61c82a1c3e7efd@syzkaller.appspotmail.com>,
bridge@lists.linux-foundation.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in fdb_find_rcu
Date: Sun, 30 Dec 2018 13:34:34 +0200 [thread overview]
Message-ID: <663bc6d0-f6ec-796d-54bb-b9afa3c0bce1@cumulusnetworks.com> (raw)
In-Reply-To: <0000000000004e8a91057e355803@google.com>
On 30/12/2018 06:01, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 90cadbbf341d Merge git://git.kernel.org/pub/scm/linux/kern..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1745c69b400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9d41c8529d7e7362
> dashboard link: https://syzkaller.appspot.com/bug?extid=017b1f61c82a1c3e7efd
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15babaab400000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14c6142d400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+017b1f61c82a1c3e7efd@syzkaller.appspotmail.com
>
Ah yes, good catch. We've missed this obvious bug during the review.
A patch is on its way, just need to run a few tests.
Cheers,
Nik
prev parent reply other threads:[~2018-12-30 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 4:01 syzbot
2018-12-30 11:34 ` Nikolay Aleksandrov [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=663bc6d0-f6ec-796d-54bb-b9afa3c0bce1@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=syzbot+017b1f61c82a1c3e7efd@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
all inboxes | Powered by JetHome®