From: David Miller <davem@davemloft.net>
To: sergei.shtylyov@cogentembedded.com
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
Subject: Re: [PATCH v3] neighbour: confirm neigh entries when ARP packet is received
Date: Thu, 13 Sep 2018 12:02:41 -0700 (PDT) [thread overview]
Message-ID: <20180913.120241.924379440079172532.davem@davemloft.net> (raw)
In-Reply-To: <16ad730b-ef79-62b0-4b11-9473c0b033e1@cogentembedded.com>
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.
next prev parent reply other threads:[~2018-09-13 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 18:12 [PATCH v3] neighbour: confirm neigh entries when ARP packet is received Vasily Khoruzhick
2018-09-13 18:26 ` Sergei Shtylyov
2018-09-13 19:02 ` David Miller [this message]
2018-09-13 19:10 ` Vasiliy Khoruzhick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180913.120241.924379440079172532.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=anarsoul@gmail.com \
--cc=edumazet@google.com \
--cc=ihrachys@redhat.com \
--cc=jwestfall@surrealistic.net \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=stephen@networkplumber.org \
--cc=vasilykh@arista.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).