Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Paolo Abeni
On Thu, 2017-05-04 at 15:49 +0200, Andrey Konovalov wrote: > On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > > Andrey Konovalov wrote: > > > > [ CC Paolo ] > > > > > I've got the following error report while fuzzing the kernel with > > >

Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Paolo Abeni
On Thu, 2017-05-04 at 15:49 +0200, Andrey Konovalov wrote: > On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > > Andrey Konovalov wrote: > > > > [ CC Paolo ] > > > > > I've got the following error report while fuzzing the kernel with > > > syzkaller. > > > > > > On commit

Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Andrey Konovalov
On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > Andrey Konovalov wrote: > > [ CC Paolo ] > >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). >> >>

Re: net: possible deadlock in skb_queue_tail

2017-05-04 Thread Andrey Konovalov
On Fri, Feb 24, 2017 at 3:56 AM, Florian Westphal wrote: > Andrey Konovalov wrote: > > [ CC Paolo ] > >> I've got the following error report while fuzzing the kernel with syzkaller. >> >> On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). >> >> Unfortunately I can't reproduce it. > >

Re: net: possible deadlock in skb_queue_tail

2017-02-23 Thread Florian Westphal
Andrey Konovalov wrote: [ CC Paolo ] > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). > > Unfortunately I can't reproduce it. This needs NETLINK_BROADCAST_ERROR enabled on a

Re: net: possible deadlock in skb_queue_tail

2017-02-23 Thread Florian Westphal
Andrey Konovalov wrote: [ CC Paolo ] > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). > > Unfortunately I can't reproduce it. This needs NETLINK_BROADCAST_ERROR enabled on a netlink socket that then

Re: net: possible deadlock in skb_queue_tail

2017-02-20 Thread Cong Wang
On Mon, Feb 20, 2017 at 5:29 AM, Andrey Konovalov wrote: > other info that might help us debug this: > > Possible unsafe locking scenario: > >CPU0CPU1 > > lock(&(>lock)->rlock); >

Re: net: possible deadlock in skb_queue_tail

2017-02-20 Thread Cong Wang
On Mon, Feb 20, 2017 at 5:29 AM, Andrey Konovalov wrote: > other info that might help us debug this: > > Possible unsafe locking scenario: > >CPU0CPU1 > > lock(&(>lock)->rlock); >

net: possible deadlock in skb_queue_tail

2017-02-20 Thread Andrey Konovalov
Hi, I've got the following error report while fuzzing the kernel with syzkaller. On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). Unfortunately I can't reproduce it. == [ INFO: possible circular locking dependency detected ]

net: possible deadlock in skb_queue_tail

2017-02-20 Thread Andrey Konovalov
Hi, I've got the following error report while fuzzing the kernel with syzkaller. On commit c470abd4fde40ea6a0846a2beab642a578c0b8cd (4.10). Unfortunately I can't reproduce it. == [ INFO: possible circular locking dependency detected ]