On Sun, Jan 29, 2017 at 2:11 AM, Dmitry Vyukov wrote:
> On Fri, Dec 9, 2016 at 6:08 AM, Cong Wang wrote:
Chain exists of:
Possible unsafe locking scenario:
CPU0CPU1
lock(genl_mutex);
On Fri, Dec 9, 2016 at 6:08 AM, Cong Wang wrote:
>>> Chain exists of:
>>> Possible unsafe locking scenario:
>>>
>>>CPU0CPU1
>>>
>>> lock(genl_mutex);
>>>lock(nlk->cb_mutex);
>>>
On Fri, Dec 9, 2016 at 6:08 AM, Cong Wang wrote:
> On Thu, Dec 8, 2016 at 4:32 PM, Cong Wang wrote:
>> On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote:
>>> Chain exists of:
>>> Possible unsafe locking scenario:
>>>
>>>CPU0CPU1
>>>-
On Thu, Dec 8, 2016 at 4:32 PM, Cong Wang wrote:
> On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote:
>> Chain exists of:
>> Possible unsafe locking scenario:
>>
>>CPU0CPU1
>>
>> lock(genl_mutex);
>>
On Thu, Dec 8, 2016 at 9:16 AM, Dmitry Vyukov wrote:
> Chain exists of:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock(genl_mutex);
>lock(nlk->cb_mutex);
>lo
On Thu, Dec 8, 2016 at 10:02 AM, Dmitry Vyukov wrote:
> Chain exists of:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock(nlk->cb_mutex);
>lock(&table[i].mutex);
>
On Thu, Dec 8, 2016 at 6:16 PM, Dmitry Vyukov wrote:
> On Thu, Dec 8, 2016 at 5:16 PM, Dmitry Vyukov wrote:
>> On Tue, Nov 29, 2016 at 6:59 AM, wrote:
Issue was reported yesterday and is under investigation.
http://marc.info/?l=linux-netdev&m=148014004331663&w=2
>>
On Thu, Dec 8, 2016 at 5:16 PM, Dmitry Vyukov wrote:
> On Tue, Nov 29, 2016 at 6:59 AM, wrote:
>>>
>>> Issue was reported yesterday and is under investigation.
>>>
>>>
>>> http://marc.info/?l=linux-netdev&m=148014004331663&w=2
>>>
>>>
>>> Thanks !
>>
>>
>> Hi Dmitry
>>
>> Can you try the patch b
On Tue, Nov 29, 2016 at 6:59 AM, wrote:
>>
>> Issue was reported yesterday and is under investigation.
>>
>>
>> http://marc.info/?l=linux-netdev&m=148014004331663&w=2
>>
>>
>> Thanks !
>
>
> Hi Dmitry
>
> Can you try the patch below with your reproducer? I haven't seen similar
> crashes reported
On Mon, 2016-11-28 at 22:59 -0700, subas...@codeaurora.org wrote:
> >
> > Issue was reported yesterday and is under investigation.
> >
> >
> > http://marc.info/?l=linux-netdev&m=148014004331663&w=2
> >
> >
> > Thanks !
>
> Hi Dmitry
>
> Can you try the patch below with your reproducer? I hav
Issue was reported yesterday and is under investigation.
http://marc.info/?l=linux-netdev&m=148014004331663&w=2
Thanks !
Hi Dmitry
Can you try the patch below with your reproducer? I haven't seen similar
crashes reported after this (or even with Eric's patch).
https://patchwork.ozlabs.o
On Sat, Nov 26, 2016 at 9:04 AM, Dmitry Vyukov wrote:
> Hello,
>
> The following program triggers deadlock warnings on genl_mutex:
>
> https://gist.githubusercontent.com/dvyukov/65e33d053e507d2ab0bf6ae83d989585/raw/b3c640ec58e894b50bcbf255c471406466cfa5d0/gistfile1.txt
>
> On commit 16ae16c6e5616c
Hello,
The following program triggers deadlock warnings on genl_mutex:
https://gist.githubusercontent.com/dvyukov/65e33d053e507d2ab0bf6ae83d989585/raw/b3c640ec58e894b50bcbf255c471406466cfa5d0/gistfile1.txt
On commit 16ae16c6e5616c084168740990fc508bda6655d4 (Nov 24).
BUG: sleeping function calle
13 matches
Mail list logo