From: Stephen Hemminger <stephen@networkplumber.org>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCHv2 iproute2 net-next] ip neigh: allow flush FAILED neighbour entry
Date: Fri, 16 Jun 2017 09:01:30 -0700 [thread overview]
Message-ID: <20170616090130.78045dcb@xeon-e3> (raw)
In-Reply-To: <1497583912-27981-1-git-send-email-liuhangbin@gmail.com>
On Fri, 16 Jun 2017 11:31:52 +0800
Hangbin Liu <liuhangbin@gmail.com> wrote:
> After upstream commit 5071034e4af7 ('neigh: Really delete an arp/neigh entry
> on "ip neigh delete" or "arp -d"'), we could delete a single FAILED neighbour
> entry now. But `ip neigh flush` still skip the FAILED entry.
>
> Move the filter after first round flush so we can flush FAILED entry on fixed
> kernel and also do not keep retrying on old kernel.
>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2017-06-16 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 8:31 [PATCH iproute2 net-next] ip neigh: allow flush FAILED neighbour entry Hangbin Liu
2017-06-14 16:54 ` Stephen Hemminger
2017-06-15 2:30 ` Hangbin Liu
2017-06-15 15:30 ` Stephen Hemminger
2017-06-16 3:31 ` [PATCHv2 " Hangbin Liu
2017-06-16 16:01 ` Stephen Hemminger [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=20170616090130.78045dcb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.