Re: net: sleeping function called from invalid context in net_enable_timestamp

2017-03-01 Thread Eric Dumazet
On Wed, 2017-03-01 at 12:07 -0800, Eric Dumazet wrote: > On Wed, 2017-03-01 at 11:59 -0800, Eric Dumazet wrote: > > On Wed, Mar 1, 2017 at 11:51 AM, Dmitry Vyukov wrote: > > > > > > Hello, > > > > > > I've got the following report while running syzkaller fuzzer on > > > e5d56efc97f8240d0b5d66c0394

Re: net: sleeping function called from invalid context in net_enable_timestamp

2017-03-01 Thread Eric Dumazet
On Wed, 2017-03-01 at 11:59 -0800, Eric Dumazet wrote: > On Wed, Mar 1, 2017 at 11:51 AM, Dmitry Vyukov wrote: > > > > Hello, > > > > I've got the following report while running syzkaller fuzzer on > > e5d56efc97f8240d0b5d66c03949382b6d7e5570 > > > > Right, a listener is playing fool games. >

Re: net: sleeping function called from invalid context in net_enable_timestamp

2017-03-01 Thread Eric Dumazet
On Wed, Mar 1, 2017 at 11:51 AM, Dmitry Vyukov wrote: > > Hello, > > I've got the following report while running syzkaller fuzzer on > e5d56efc97f8240d0b5d66c03949382b6d7e5570 Right, a listener is playing fool games. We need to use a work queue for all net_enable_timestamp() invocations

net: sleeping function called from invalid context in net_enable_timestamp

2017-03-01 Thread Dmitry Vyukov
Hello, I've got the following report while running syzkaller fuzzer on e5d56efc97f8240d0b5d66c03949382b6d7e5570: BUG: sleeping function called from invalid context at kernel/locking/mutex.c:745 in_atomic(): 1, irqs_disabled(): 0, pid: 23233, name: syz-executor5 INFO: lockdep is turned off. CPU: 1