From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vasiliy Khoruzhick Subject: Re: [PATCH v3] neighbour: confirm neigh entries when ARP packet is received Date: Thu, 13 Sep 2018 12:10:04 -0700 Message-ID: References: <20180913181203.4207-1-vasilykh@arista.com> <16ad730b-ef79-62b0-4b11-9473c0b033e1@cogentembedded.com> <20180913.120241.924379440079172532.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: sergei.shtylyov@cogentembedded.com, Roopa Prabhu , Alexey Dobriyan , Eric Dumazet , Stephen Hemminger , Jim Westfall , Wolfgang Bumiller , Vasily Khoruzhick , Kees Cook , Ihar Hrachyshka , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: David Miller Return-path: In-Reply-To: <20180913.120241.924379440079172532.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Sep 13, 2018 at 12:02 PM, David Miller wrote: > From: Sergei Shtylyov > 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 >> [...] > > Applied and queued up for -stable. Thanks!