From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: torvalds@linux-foundation.org, andreyknvl@google.com,
edumazet@google.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
yoshfuji@linux-ipv6.org, kaber@trash.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, alexander.h.duyck@intel.com,
dsa@cumulusnetworks.com, daniel@iogearbox.net, me@tobin.cc,
jiri@mellanox.com, stephen@networkplumber.org,
dvyukov@google.com, kcc@google.com, syzkaller@googlegroups.com
Subject: Re: net/core: BUG in unregister_netdevice_many
Date: Fri, 21 Apr 2017 15:38:40 -0400 (EDT) [thread overview]
Message-ID: <20170421.153840.2181333362371190008.davem@davemloft.net> (raw)
In-Reply-To: <CAM_iQpUoWzeZPSKTCm13tumvOa7fLMJnz_0F_LSq4odYvWtRaQ@mail.gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Fri, 21 Apr 2017 11:55:04 -0700
> On Fri, Apr 21, 2017 at 10:25 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Fri, Apr 21, 2017 at 5:48 AM, Andrey Konovalov <andreyknvl@google.com> wrote:
>>>
>>> I've got the following error report while fuzzing the kernel with syzkaller.
>>>
>>> ------------[ cut here ]------------
>>> kernel BUG at net/core/dev.c:6813!
>>
>> Another useless BUG_ON() that
>
> I think we are double-unregister'ing the pim6reg device,
> we probably need something like:
This particular bug is fixed by Nikolay's fix.
I'm not saying you haven't spotted another bug.
next prev parent reply other threads:[~2017-04-21 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:48 net/core: BUG in unregister_netdevice_many Andrey Konovalov
2017-04-21 17:25 ` Linus Torvalds
2017-04-21 17:42 ` Linus Torvalds
2017-04-21 18:30 ` Nikolay Aleksandrov
2017-04-21 19:37 ` David Miller
2017-04-21 18:55 ` Cong Wang
2017-04-21 19:38 ` David Miller [this message]
2017-04-21 17:42 ` [PATCH net] ip6mr: fix notification device destruction Nikolay Aleksandrov
2017-04-21 18:30 ` Nikolay Aleksandrov
2017-04-21 18:46 ` Andrey Konovalov
2017-04-21 19:36 ` David Miller
2017-04-21 19:50 ` Nikolay Aleksandrov
2017-04-21 19:55 ` David Miller
2017-04-21 19:56 ` Nikolay Aleksandrov
2017-04-21 19:58 ` David Miller
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=20170421.153840.2181333362371190008.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=andreyknvl@google.com \
--cc=daniel@iogearbox.net \
--cc=dsa@cumulusnetworks.com \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=jiri@mellanox.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kcc@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=syzkaller@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yoshfuji@linux-ipv6.org \
/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