[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cdfcb6f4-f2db-b710-1b6d-cf15b022c2d3@virtuozzo.com>
Date: Mon, 19 Feb 2018 17:41:54 +0300
From: Kirill Tkhai <ktkhai@...tuozzo.com>
To: Jon Maloy <jon.maloy@...csson.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
syzbot <syzbot+749d9d87c294c00ca856@...kaller.appspotmail.com>,
Ying Xue <ying.xue@...driver.com>
Cc: Andrei Vagin <avagin@...tuozzo.com>,
David Miller <davem@...emloft.net>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Florian Westphal <fw@...len.de>,
LKML <linux-kernel@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
"roman.kapl@...go.com" <roman.kapl@...go.com>,
"syzkaller-bugs@...glegroups.com" <syzkaller-bugs@...glegroups.com>,
"tipc-discussion@...ts.sourceforge.net"
<tipc-discussion@...ts.sourceforge.net>
Subject: Re: BUG: sleeping function called from invalid context at
net/core/sock.c:LINE (3)
On 19.02.2018 16:23, Jon Maloy wrote:
> I don't understand this one. tipc_topsrv_stop() can only be trigged from a user doing rmmod(), and I double checked that this is running in user mode.
> How does the call chain you are reporting occur?
>
In case of CONFIG_NET_NS=y, pernet_operations::exit() is called after last reference
to a net is dropped. So, this may happen not only on module unload path.
Kirill
>
>
>> -----Original Message-----
>> From: Kirill Tkhai [mailto:ktkhai@...tuozzo.com]
>> Sent: Saturday, February 17, 2018 23:23
>> To: Dmitry Vyukov <dvyukov@...gle.com>; syzbot
>> <syzbot+749d9d87c294c00ca856@...kaller.appspotmail.com>; Jon Maloy
>> <jon.maloy@...csson.com>; Ying Xue <ying.xue@...driver.com>
>> Cc: Andrei Vagin <avagin@...tuozzo.com>; David Miller
>> <davem@...emloft.net>; Eric W. Biederman <ebiederm@...ssion.com>;
>> Florian Westphal <fw@...len.de>; LKML <linux-kernel@...r.kernel.org>;
>> netdev <netdev@...r.kernel.org>; Nicolas Dichtel
>> <nicolas.dichtel@...nd.com>; roman.kapl@...go.com; syzkaller-
>> bugs@...glegroups.com; tipc-discussion@...ts.sourceforge.net
>> Subject: Re: BUG: sleeping function called from invalid context at
>> net/core/sock.c:LINE (3)
>>
>> On 17.02.2018 11:15, Dmitry Vyukov wrote:
>>> On Sat, Feb 17, 2018 at 4:00 AM, syzbot
>>> <syzbot+749d9d87c294c00ca856@...kaller.appspotmail.com> wrote:
>>>> Hello,
>>>>
>>>> syzbot hit the following crash on net-next commit
>>>> 65bd449c32c2745df61913ab54087e77f9d9b70d (Fri Feb 16 20:26:35 2018
>>>> +0000) Merge branch 'tipc-de-generealize-topology-server'
>>>
>>> +tipc maintainers
>>
>> This looks to be caused by commit 0ef897be12b8
>> "tipc: separate topology server listener socket from subcsriber sockets"
>>
>> Thanks,
>> Kirill
Powered by blists - more mailing lists