From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: syzbot <syzbot+2add91c08eb181fea1bf@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: memory leak in fdb_create (2)
Date: Mon, 2 Dec 2019 22:20:38 +0200 [thread overview]
Message-ID: <76434004-ca0b-0917-78bd-a0332af2a716@cumulusnetworks.com> (raw)
In-Reply-To: <0000000000001821bf0598bb955c@google.com>
On 02/12/2019 19:05, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: ceb30747 Merge tag 'y2038-cleanups-5.5' of git://git.kerne..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=142b3e7ee00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=26f873e40f2b4134
> dashboard link: https://syzkaller.appspot.com/bug?extid=2add91c08eb181fea1bf
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12976feee00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10604feee00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+2add91c08eb181fea1bf@syzkaller.appspotmail.com
>
> BUG: memory leak
> unreferenced object 0xffff888124fa7080 (size 128):
> comm "syz-executor163", pid 7170, jiffies 4294954254 (age 12.500s)
I'll look into this tomorrow, I think see the issue.
Thanks!
prev parent reply other threads:[~2019-12-02 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 17:05 memory leak in fdb_create (2) syzbot
2019-12-02 20:20 ` 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=76434004-ca0b-0917-78bd-a0332af2a716@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+2add91c08eb181fea1bf@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).