On Wed, Oct 19, 2016 at 12:45 AM, Baozeng Ding wrote:
> It fixes the issue for me.
> Tested-by: Baozeng Ding
Thanks for testing, I will send out the patch formally very soon.
BTW, you can check mailing archive to see if your email succeeds or not,
for example, http://marc.info/?l=linux-netdev
It fixes the issue for me.
Tested-by: Baozeng Ding
On 2016/10/17 17:54, Baozeng Ding wrote:
> Applied the patch to my test tree. I will tell you the result a few days
> later. Thank you.
>
> On 2016/10/17 2:50, Cong Wang wrote:
>> On Sun, Oct 16, 2016 at 6:34 AM, Baozeng Ding wrote:
>>> Poss
It fixes the issue for me.
Tested-by: Baozeng Ding
On 2016/10/17 17:54, Baozeng Ding wrote:
> Applied the patch to my test tree. I will tell you the result a few days
> later. Thank you.
>
> On 2016/10/17 2:50, Cong Wang wrote:
>> On Sun, Oct 16, 2016 at 6:34 AM, Baozeng Ding wrote:
>>> Pos
Applied the patch to my test tree. I will tell you the result a few days later.
Thank you.
On 2016/10/17 2:50, Cong Wang wrote:
> On Sun, Oct 16, 2016 at 6:34 AM, Baozeng Ding wrote:
>> Possible unsafe locking scenario:
>>
>>CPU0CPU1
>>
On Sun, Oct 16, 2016 at 6:34 AM, Baozeng Ding wrote:
> Possible unsafe locking scenario:
>
>CPU0CPU1
>
> lock([ 165.136033] sk_lock-AF_INET6
> );
>lock([ 165.136033] rtnl_mutex
> );
>
Hello,
While running syzkaller fuzzer I have got the following deadlock
report. The kernel version is 4.8.0+ (on Oct 7 commit
d1f5323370fceaed43a7ee38f4c7bfc7e70f28d0). Unfortunately I failed to find a
reproducer for it.
===
