On Wed, Apr 12, 2017 at 9:41 PM, Cong Wang wrote:
> On Wed, Apr 12, 2017 at 5:05 AM, Andrey Konovalov
> wrote:
>> Hi Cong,
>>
>> I now have a reproducer for this bug (attached) and your patch fixes it.
>>
>> Could you send it?
>>
>
> Done. I verified it with your reproducer too.
>
> Thanks!
Gre
On Wed, Apr 12, 2017 at 5:05 AM, Andrey Konovalov wrote:
> Hi Cong,
>
> I now have a reproducer for this bug (attached) and your patch fixes it.
>
> Could you send it?
>
Done. I verified it with your reproducer too.
Thanks!
On Mon, Mar 6, 2017 at 3:04 AM, Cong Wang wrote:
> On Fri, Mar 3, 2017 at 10:43 AM, Dmitry Vyukov wrote:
>> On Thu, Mar 2, 2017 at 10:40 AM, Dmitry Vyukov wrote:
>>> On Wed, Mar 1, 2017 at 6:18 PM, Cong Wang wrote:
On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
> Hello,
>
>>
On Fri, Mar 3, 2017 at 10:43 AM, Dmitry Vyukov wrote:
> On Thu, Mar 2, 2017 at 10:40 AM, Dmitry Vyukov wrote:
>> On Wed, Mar 1, 2017 at 6:18 PM, Cong Wang wrote:
>>> On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
Hello,
I've got the following deadlock report while running s
On Thu, Mar 2, 2017 at 10:40 AM, Dmitry Vyukov wrote:
> On Wed, Mar 1, 2017 at 6:18 PM, Cong Wang wrote:
>> On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> I've got the following deadlock report while running syzkaller fuzzer
>>> on linux-next/51788aebe7cae79cb334ad506413
On Fri, Mar 3, 2017 at 7:43 PM, Dmitry Vyukov wrote:
> On Thu, Mar 2, 2017 at 10:40 AM, Dmitry Vyukov wrote:
>> On Wed, Mar 1, 2017 at 6:18 PM, Cong Wang wrote:
>>> On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
Hello,
I've got the following deadlock report while running sy
On Wed, Mar 1, 2017 at 6:18 PM, Cong Wang wrote:
> On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
>> Hello,
>>
>> I've got the following deadlock report while running syzkaller fuzzer
>> on linux-next/51788aebe7cae79cb334ad50641347465fc188fd:
>>
>> ==
On Wed, Mar 1, 2017 at 2:44 AM, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following deadlock report while running syzkaller fuzzer
> on linux-next/51788aebe7cae79cb334ad50641347465fc188fd:
>
> ==
> [ INFO: possible circular locking dependenc
Hello,
I've got the following deadlock report while running syzkaller fuzzer
on linux-next/51788aebe7cae79cb334ad50641347465fc188fd:
==
[ INFO: possible circular locking dependency detected ]
4.10.0-next-20170301+ #1 Not tainted