On Wed, Mar 15, 2017 at 7:19 PM, Cong Wang wrote:
> On Wed, Mar 15, 2017 at 5:52 AM, Marcelo Ricardo Leitner
> wrote:
>> On Tue, Mar 14, 2017 at 09:52:15PM -0700, Cong Wang wrote:
>>> Instead of checking for the status of the sock, I believe the following
>>> one-line fix should do the trick too.
On Wed, Mar 15, 2017 at 5:52 AM, Marcelo Ricardo Leitner
wrote:
> On Tue, Mar 14, 2017 at 09:52:15PM -0700, Cong Wang wrote:
>> Instead of checking for the status of the sock, I believe the following
>> one-line fix should do the trick too. Can you give it a try?
>>
>> diff --git a/net/sctp/socket
On Tue, Mar 14, 2017 at 09:52:15PM -0700, Cong Wang wrote:
> On Fri, Mar 10, 2017 at 12:04 PM, Dmitry Vyukov wrote:
> > On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
> > wrote:
> >> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
> >>> Hello,
> >>>
> >>> I've got the following r
On Wed, Mar 15, 2017 at 5:52 AM, Cong Wang wrote:
> On Fri, Mar 10, 2017 at 12:04 PM, Dmitry Vyukov wrote:
>> On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
>> wrote:
>>> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
Hello,
I've got the following recursive locki
On Fri, Mar 10, 2017 at 12:04 PM, Dmitry Vyukov wrote:
> On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
> wrote:
>> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> I've got the following recursive locking report while running
>>> syzkaller fuzzer on net-next/9c
On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
wrote:
> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
>> Hello,
>>
>> I've got the following recursive locking report while running
>> syzkaller fuzzer on net-next/9c28286b1b4b9bce6e35dd4c8a1265f03802a89a:
>>
>> [ INFO: possible re
On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following recursive locking report while running
> syzkaller fuzzer on net-next/9c28286b1b4b9bce6e35dd4c8a1265f03802a89a:
>
> [ INFO: possible recursive locking detected ]
> 4.10.0+ #14 Not tainted
> --
Hello,
I've got the following recursive locking report while running
syzkaller fuzzer on net-next/9c28286b1b4b9bce6e35dd4c8a1265f03802a89a:
[ INFO: possible recursive locking detected ]
4.10.0+ #14 Not tainted
-
syz-executor3/5560 is trying to acquire l