From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH v3] neighbour: confirm neigh entries when ARP packet is
 received
Date: Thu, 13 Sep 2018 12:02:41 -0700 (PDT)
Message-ID: <20180913.120241.924379440079172532.davem@davemloft.net>
References: <20180913181203.4207-1-vasilykh@arista.com>
        <16ad730b-ef79-62b0-4b11-9473c0b033e1@cogentembedded.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: vasilykh@arista.com, roopa@cumulusnetworks.com,
        adobriyan@gmail.com, edumazet@google.com,
        stephen@networkplumber.org, jwestfall@surrealistic.net,
        w.bumiller@proxmox.com, anarsoul@gmail.com, keescook@chromium.org,
        ihrachys@redhat.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
To: sergei.shtylyov@cogentembedded.com
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <16ad730b-ef79-62b0-4b11-9473c0b033e1@cogentembedded.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.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@arista.com>
> [...]

Applied and queued up for -stable.