Re: dccp: potential deadlock in dccp_v4_ctl_send_reset

2016-07-05 Thread Eric Dumazet
On Tue, 2016-07-05 at 10:17 -0700, Cong Wang wrote: > On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote: > > other info that might help us debug this: > > Possible unsafe locking scenario: > > > >CPU0 > > > > lock(slock-AF_INET); > > > >

Re: dccp: potential deadlock in dccp_v4_ctl_send_reset

2016-07-05 Thread Cong Wang
On Tue, Jul 5, 2016 at 4:59 AM, Dmitry Vyukov wrote: > other info that might help us debug this: > Possible unsafe locking scenario: > >CPU0 > > lock(slock-AF_INET); > > lock(slock-AF_INET); > > *** DEADLOCK *** > > 1 lock held by

dccp: potential deadlock in dccp_v4_ctl_send_reset

2016-07-05 Thread Dmitry Vyukov
Hello, While running syzkaller fuzzer I've got the following deadlock report: = [ INFO: inconsistent lock state ] 4.7.0-rc5+ #28 Not tainted - inconsistent {IN-SOFTIRQ-W} -> {SOFTIRQ-ON-W} usage. syz-executor/354