From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Vasily Khoruzhick <vasilykh@arista.com>,
"David S. Miller" <davem@davemloft.net>,
Roopa Prabhu <roopa@cumulusnetworks.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Jim Westfall <jwestfall@surrealistic.net>,
Wolfgang Bumiller <w.bumiller@proxmox.com>,
Vasily Khoruzhick <anarsoul@gmail.com>,
Kees Cook <keescook@chromium.org>,
Ihar Hrachyshka <ihrachys@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] neighbour: confirm neigh entries when ARP packet is received
Date: Wed, 12 Sep 2018 12:05:00 +0300 [thread overview]
Message-ID: <11ed0447-bcf9-8590-94bb-1a4b842ee002@cogentembedded.com> (raw)
In-Reply-To: <20180911180406.31283-1-vasilykh@arista.com>
Hello!
On 9/11/2018 9:04 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 to sense not to confirm it when ARP packet is
"Makes sense" or "makes no sense"?
> received.
>
> Fixes: 77d7123342 ("neighbour: update neigh timestamps iff update is
> effective")
>
> Signed-off-by: Vasily Khoruzhick <vasilykh@arista.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2018-09-12 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 18:04 [PATCH v2] neighbour: confirm neigh entries when ARP packet is received Vasily Khoruzhick
2018-09-11 18:12 ` Stephen Hemminger
2018-09-11 18:23 ` Vasiliy Khoruzhick
2018-09-12 9:05 ` Sergei Shtylyov [this message]
2018-09-13 16:04 ` David Miller
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=11ed0447-bcf9-8590-94bb-1a4b842ee002@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=adobriyan@gmail.com \
--cc=anarsoul@gmail.com \
--cc=davem@davemloft.net \
--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=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).