[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180913.120241.924379440079172532.davem@davemloft.net>
Date: Thu, 13 Sep 2018 12:02:41 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: sergei.shtylyov@...entembedded.com
Cc: vasilykh@...sta.com, roopa@...ulusnetworks.com,
adobriyan@...il.com, edumazet@...gle.com,
stephen@...workplumber.org, jwestfall@...realistic.net,
w.bumiller@...xmox.com, anarsoul@...il.com, keescook@...omium.org,
ihrachys@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] neighbour: confirm neigh entries when ARP packet is
received
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Date: Thu, 13 Sep 2018 21:26:42 +0300
> Hello!
>
> On 09/13/2018 09:12 PM, Vasily Khoruzhick wrote:
>
>> Update 'confirmed' timestamp when ARP packet is received. It shouldn't
>> affect locktime logic and anyway entry can be confirmed by any higher-layer
>> protocol. Thus it makes sense to confirm it when ARP packet is received.
>>
>> Fixes: 77d7123342 ("neighbour: update neigh timestamps iff update is effective")
>
> Need at least 12 hex digits... Perhaps could be fixed when applying?
Yeah I took care of that.
>
>> Signed-off-by: Vasily Khoruzhick <vasilykh@...sta.com>
> [...]
Applied and queued up for -stable.
Powered by blists - more mailing lists