a...@davemloft.net>; Eric W. Biederman <ebied...@xmission.com>;
>> Florian Westphal <f...@strlen.de>; LKML <linux-ker...@vger.kernel.org>;
>> netdev <netdev@vger.kernel.org>; Nicolas Dichtel
>> <nicolas.dich...@6wind.com>; roman.k...@sysgo.com; syzkal
On Mon, 2018-02-19 at 13: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?
tipc_topsrv_stop() is called also at
nicolas.dich...@6wind.com>; roman.k...@sysgo.com; syzkaller-
>> b...@googlegroups.com; tipc-discuss...@lists.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
k...@sysgo.com; syzkaller-
> b...@googlegroups.com; tipc-discuss...@lists.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
On 17.02.2018 11:15, Dmitry Vyukov wrote:
> On Sat, Feb 17, 2018 at 4:00 AM, syzbot
> wrote:
>> Hello,
>>
>> syzbot hit the following crash on net-next commit
>> 65bd449c32c2745df61913ab54087e77f9d9b70d (Fri Feb 16 20:26:35 2018 +)
>>