From: Vitaly Kuznetsov
Date: Fri, 21 Oct 2016 17:17:18 +0200
> David Miller writes:
>
>> From: Vitaly Kuznetsov
>> Date: Fri, 21 Oct 2016 13:15:53 +0200
>>
>>> David Miller writes:
>>>
From: Vitaly
From: Vitaly Kuznetsov
Date: Fri, 21 Oct 2016 17:17:18 +0200
> David Miller writes:
>
>> From: Vitaly Kuznetsov
>> Date: Fri, 21 Oct 2016 13:15:53 +0200
>>
>>> David Miller writes:
>>>
From: Vitaly Kuznetsov
Date: Thu, 20 Oct 2016 10:51:04 +0200
> Stephen Hemminger
From: Vitaly Kuznetsov
Date: Wed, 19 Oct 2016 15:53:01 +0200
> Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
> chn_table") turns out to be incomplete. A crash in
> netvsc_get_next_send_section() is observed on mtu change when the device
> is under
From: Vitaly Kuznetsov
Date: Wed, 19 Oct 2016 15:53:01 +0200
> Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
> chn_table") turns out to be incomplete. A crash in
> netvsc_get_next_send_section() is observed on mtu change when the device
> is under load. The race I
David Miller writes:
> From: Vitaly Kuznetsov
> Date: Fri, 21 Oct 2016 13:15:53 +0200
>
>> David Miller writes:
>>
>>> From: Vitaly Kuznetsov
>>> Date: Thu, 20 Oct 2016 10:51:04 +0200
>>>
Stephen
David Miller writes:
> From: Vitaly Kuznetsov
> Date: Fri, 21 Oct 2016 13:15:53 +0200
>
>> David Miller writes:
>>
>>> From: Vitaly Kuznetsov
>>> Date: Thu, 20 Oct 2016 10:51:04 +0200
>>>
Stephen Hemminger writes:
> Do we need ACCESS_ONCE() here to avoid check/use issues?
From: Vitaly Kuznetsov
Date: Fri, 21 Oct 2016 13:15:53 +0200
> David Miller writes:
>
>> From: Vitaly Kuznetsov
>> Date: Thu, 20 Oct 2016 10:51:04 +0200
>>
>>> Stephen Hemminger writes:
>>>
Do we
From: Vitaly Kuznetsov
Date: Fri, 21 Oct 2016 13:15:53 +0200
> David Miller writes:
>
>> From: Vitaly Kuznetsov
>> Date: Thu, 20 Oct 2016 10:51:04 +0200
>>
>>> Stephen Hemminger writes:
>>>
Do we need ACCESS_ONCE() here to avoid check/use issues?
>>>
>>> I think we don't: this is
David Miller writes:
> From: Vitaly Kuznetsov
> Date: Thu, 20 Oct 2016 10:51:04 +0200
>
>> Stephen Hemminger writes:
>>
>>> Do we need ACCESS_ONCE() here to avoid check/use issues?
>>>
>>
>> I think we don't: this is the only
David Miller writes:
> From: Vitaly Kuznetsov
> Date: Thu, 20 Oct 2016 10:51:04 +0200
>
>> Stephen Hemminger writes:
>>
>>> Do we need ACCESS_ONCE() here to avoid check/use issues?
>>>
>>
>> I think we don't: this is the only place in the function where we read
>> the variable so we'll get
From: Vitaly Kuznetsov
Date: Thu, 20 Oct 2016 10:51:04 +0200
> Stephen Hemminger writes:
>
>> Do we need ACCESS_ONCE() here to avoid check/use issues?
>>
>
> I think we don't: this is the only place in the function where we read
> the variable so
From: Vitaly Kuznetsov
Date: Thu, 20 Oct 2016 10:51:04 +0200
> Stephen Hemminger writes:
>
>> Do we need ACCESS_ONCE() here to avoid check/use issues?
>>
>
> I think we don't: this is the only place in the function where we read
> the variable so we'll get normal read. We're not trying to
kernel@vger.kernel.org; KY Srinivasan <k...@microsoft.com>; Haiyang Zhang
<haiya...@microsoft.com>
Subject: [PATCH net-next] hv_netvsc: fix a race between netvsc_send() and
netvsc_init_buf()
Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
chn_table"
Srinivasan ; Haiyang Zhang
Subject: [PATCH net-next] hv_netvsc: fix a race between netvsc_send() and
netvsc_init_buf()
Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
chn_table") turns out to be incomplete. A crash in
netvsc_get_next_send_section() is observed on
kernel.org
> Cc: Stephen Hemminger <sthem...@microsoft.com>; de...@linuxdriverproject.org;
> linux-kernel@vger.kernel.org; KY Srinivasan <k...@microsoft.com>; Haiyang
> Zhang <haiya...@microsoft.com>
> Subject: [PATCH net-next] hv_netvsc: fix a race between ne
tephen Hemminger ; de...@linuxdriverproject.org;
> linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang
> Zhang
> Subject: [PATCH net-next] hv_netvsc: fix a race between netvsc_send() and
> netvsc_init_buf()
>
> Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populat
Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
chn_table") turns out to be incomplete. A crash in
netvsc_get_next_send_section() is observed on mtu change when the device
is under load. The race I identified is: if we get to netvsc_send() after
we set net_device_ctx->nvdev
Fix in commit 880988348270 ("hv_netvsc: set nvdev link after populating
chn_table") turns out to be incomplete. A crash in
netvsc_get_next_send_section() is observed on mtu change when the device
is under load. The race I identified is: if we get to netvsc_send() after
we set net_device_ctx->nvdev
18 matches
Mail list logo