[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOrHB_DrV0+Tp4jgFMG45_PqgOZh-aYDEJFxT40La0v6RC2U8Q@mail.gmail.com>
Date: Fri, 28 Oct 2016 10:01:51 -0700
From: Pravin Shelar <pshelar@....org>
To: "John W. Linville" <linville@...driver.com>
Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCH net 2/2] geneve: avoid using stale geneve socket.
On Fri, Oct 28, 2016 at 7:27 AM, John W. Linville
<linville@...driver.com> wrote:
> On Thu, Oct 27, 2016 at 11:51:56AM -0700, Pravin B Shelar wrote:
>> This patch is similar to earlier vxlan patch.
>> Geneve device close operation frees geneve socket. This
>> operation can race with geneve-xmit function which
>> dereferences geneve socket. Following patch uses RCU
>> mechanism to avoid this situation.
>>
>> Signed-off-by: Pravin B Shelar <pshelar@....org>
>
> LGTM, although I reckon that Stephen's comment about RCU_INIT_POINTER
> applies to this patch as well.
>
Geneve code is bit different and it is using rcu_assign_pointer()
while destroying the object. so we need the barrier.
> Either way...
>
> Acked-by: John W. Linville <linville@...driver.com>
>
Powered by blists - more mailing lists