From: Vasiliy Khoruzhick <vasilykh@arista.com>
To: David Miller <davem@davemloft.net>
Cc: sergei.shtylyov@cogentembedded.com,
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 v3] neighbour: confirm neigh entries when ARP packet is received
Date: Thu, 13 Sep 2018 12:10:04 -0700 [thread overview]
Message-ID: <CAL0zPMNndiwJSXEjy1v8himze06fU6_AgMAN=XRnemjjxfoRQg@mail.gmail.com> (raw)
In-Reply-To: <20180913.120241.924379440079172532.davem@davemloft.net>
On Thu, Sep 13, 2018 at 12:02 PM, David Miller <davem@davemloft.net> wrote:
> 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.
Thanks!
prev parent reply other threads:[~2018-09-13 19:10 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
2018-09-13 19:10 ` Vasiliy Khoruzhick [this message]
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='CAL0zPMNndiwJSXEjy1v8himze06fU6_AgMAN=XRnemjjxfoRQg@mail.gmail.com' \
--to=vasilykh@arista.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=sergei.shtylyov@cogentembedded.com \
--cc=stephen@networkplumber.org \
--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).