mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hujunwei <hujunwei4@huawei.com>
To: David Miller <davem@davemloft.net>, <willemdebruijn.kernel@gmail.com>
Cc: <syzbot+1e8114b61079bfe9cbc5@syzkaller.appspotmail.com>,
	<jon.maloy@ericsson.com>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>, <syzkaller-bugs@googlegroups.com>,
	<tipc-discussion@lists.sourceforge.net>, <ying.xue@windriver.com>,
	<dvyukov@google.com>, <edumazet@google.com>
Subject: Re: INFO: trying to register non-static key in rhashtable_walk_enter
Date: Sun, 19 May 2019 16:55:39 +0800	[thread overview]
Message-ID: <ad7739b9-0b90-d704-ebc0-08e77a1c7d5e@huawei.com> (raw)
In-Reply-To: <20190518.131257.1124207773533732758.davem@davemloft.net>



On 2019/5/19 4:12, David Miller wrote:
> From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
> Date: Sat, 18 May 2019 14:19:07 -0400
> 
>> On Sat, May 18, 2019 at 2:09 PM Willem de Bruijn
>> <willemdebruijn.kernel@gmail.com> wrote:
>>>
>>> On Sat, May 18, 2019 at 3:34 AM syzbot
>>> <syzbot+1e8114b61079bfe9cbc5@syzkaller.appspotmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> syzbot found the following crash on:
>>>>
>>>> HEAD commit:    510e2ced ipv6: fix src addr routing with the exception table
>>>> git tree:       net
>>>> console output: https://syzkaller.appspot.com/x/log.txt?x=15b7e608a00000
>>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=82f0809e8f0a8c87
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=1e8114b61079bfe9cbc5
>>>> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
>>>>
>>>> Unfortunately, I don't have any reproducer for this crash yet.
>>>>
>>>> IMPORTANT: if you fix the bug, please add the following tag to the commit:
>>>> Reported-by: syzbot+1e8114b61079bfe9cbc5@syzkaller.appspotmail.com
>>>>
>>>> INFO: trying to register non-static key.
>>>> the code is fine but needs lockdep annotation.
>>>
>>> All these five rhashtable_walk_enter probably have the same root cause.
>>>
>>> Bisected to commit 7e27e8d6130c (" tipc: switch order of device
>>> registration to fix a crash"). Reverting that fixes it.
>>>
>>> Before the commit, tipc_init succeeds. After the commit it fails at
>>> register_pernet_subsys(&tipc_net_ops) due to error in
>>>
>>>   tipc_init_net
>>>     tipc_topsrv_start
>>>       tipc_topsrv_create_listener
>>>         sock_create_kern
>>>
>>> On a related note, in tipc_topsrv_start srv is also not freed on later
>>> error paths.
>>
>> and tipc_topsrv_stop is not called in tipc_init_net on later error paths.
> 
> This was gonna get fixed by:
> 
> 532b0f7ece4cb2ffd24dc723ddf55242d1188e5e
> tipc: fix modprobe tipc failed after switch order of device registration
> 
> I think...
> 
> But I reverted because they were still fiddling around with the fix.
> 
> This looks really bad at this point and I'm likely to revert 7e27e8d6130c
> because it creates so many more bugs than it fixes :-////
> 
> .
> 
Hi, David
I am really sorry for this, just as you said, this bug fixed by:
532b0f7ece4cb2ffd24dc723ddf55242d1188e5e
tipc: fix modprobe tipc failed after switch order of device registration.

I verified the patch v2 works fine, inclue use namespaces together.
I will update syzbot report in patch v3.

Regards,
Junwei


  reply	other threads:[~2019-05-20  0:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18  7:34 syzbot
2019-05-18 18:09 ` Willem de Bruijn
2019-05-18 18:19   ` Willem de Bruijn
2019-05-18 20:12     ` David Miller
2019-05-19  8:55       ` hujunwei [this message]
2019-05-20 22:59 ` syzbot

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=ad7739b9-0b90-d704-ebc0-08e77a1c7d5e@huawei.com \
    --to=hujunwei4@huawei.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=jon.maloy@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+1e8114b61079bfe9cbc5@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=ying.xue@windriver.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®