[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <16ad730b-ef79-62b0-4b11-9473c0b033e1@cogentembedded.com>
Date: Thu, 13 Sep 2018 21:26:42 +0300
From: Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
To: Vasily Khoruzhick <vasilykh@...sta.com>,
"David S. Miller" <davem@...emloft.net>,
Roopa Prabhu <roopa@...ulusnetworks.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Eric Dumazet <edumazet@...gle.com>,
Stephen Hemminger <stephen@...workplumber.org>,
Jim Westfall <jwestfall@...realistic.net>,
Wolfgang Bumiller <w.bumiller@...xmox.com>,
Vasily Khoruzhick <anarsoul@...il.com>,
Kees Cook <keescook@...omium.org>,
Ihar Hrachyshka <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
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?
> Signed-off-by: Vasily Khoruzhick <vasilykh@...sta.com>
[...]
MBR, Sergei
Powered by blists - more mailing lists