From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: syzbot <syzbot+88533dc8b582309bf3ee@syzkaller.appspotmail.com>,
bridge@lists.linux-foundation.org, bsingharora@gmail.com,
coreteam@netfilter.org, davem@davemloft.net, duwe@suse.de,
kaber@trash.net, kadlec@blackhole.kfki.hu,
linux-kernel@vger.kernel.org, mingo@redhat.com,
mpe@ellerman.id.au, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, pablo@netfilter.org,
roopa@cumulusnetworks.com, rostedt@goodmis.org,
syzkaller-bugs@googlegroups.com
Subject: Re: memory leak in fdb_create
Date: Sun, 28 Jul 2019 19:51:03 +0300 [thread overview]
Message-ID: <d16a3297-d651-0a32-e803-774a9c8c61bf@cumulusnetworks.com> (raw)
In-Reply-To: <0000000000008be1b2058ebe7805@google.com>
On 28/07/2019 17:20, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 04cf31a759ef575f750a63777cee95500e410994
> Author: Michael Ellerman <mpe@ellerman.id.au>
> Date: Thu Mar 24 11:04:01 2016 +0000
>
> ftrace: Make ftrace_location_range() global
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1538c778600000
> start commit: abf02e29 Merge tag 'pm-5.2-rc6' of git://git.kernel.org/pu..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1738c778600000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1338c778600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=56f1da14935c3cce
> dashboard link: https://syzkaller.appspot.com/bug?extid=88533dc8b582309bf3ee
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16de5c06a00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10546026a00000
>
> Reported-by: syzbot+88533dc8b582309bf3ee@syzkaller.appspotmail.com
> Fixes: 04cf31a759ef ("ftrace: Make ftrace_location_range() global")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
I see the problem, it'd happen if the multicast stats memory allocation fails on bridge
init then the fdb added due to the default vlan would remain and the bridge kmem cache
would be destroyed while not empty (you can even trigger a BUG because of that).
I'll post a patch shortly after running a few tests.
Thanks,
Nik
prev parent reply other threads:[~2019-07-28 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:27 memory leak in fdb_create syzbot
2019-07-28 14:20 ` syzbot
2019-07-28 16:51 ` 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=d16a3297-d651-0a32-e803-774a9c8c61bf@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=bridge@lists.linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=duwe@suse.de \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=roopa@cumulusnetworks.com \
--cc=rostedt@goodmis.org \
--cc=syzbot+88533dc8b582309bf3ee@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).