From: David Ahern <dsahern@kernel.org>
To: netdev@vger.kernel.org
Cc: idosch@mellanox.com, stephen@networkplumber.org,
David Ahern <dsahern@gmail.com>
Subject: [PATCH iproute2-next 0/5] ip bridge: Updates to neigh and fdb dumps
Date: Wed, 2 Jan 2019 20:38:27 -0800 [thread overview]
Message-ID: <20190103043832.3748-1-dsahern@kernel.org> (raw)
From: David Ahern <dsahern@gmail.com>
First 3 patches fixup ip neigh and bridge fdb dumps to use
rtnl_neighdump_req.
Patch 4 adds a new flag for commands to know when strict checking is
enabled.
Patch 5 fixes fdb dumps to work on older kernels.
David Ahern (5):
libnetlink: Add filter function to rtnl_neighdump_req
ip neigh: Convert do_show_or_flush to use rtnl_neighdump_req
bridge: Update fdb show to use rtnl_neighdump_req
libnetlink: Add RTNL_HANDLE_F_STRICT_CHK flag
bridge: fdb: Fix filtering with strict checking disabled
bridge/fdb.c | 62 +++++++++++++++++++++++++++++++++++++++-------------
include/libnetlink.h | 4 +++-
ip/ipneigh.c | 42 +++++++++++++++++++++--------------
lib/libnetlink.c | 19 +++++++++++++---
misc/arpd.c | 2 +-
5 files changed, 93 insertions(+), 36 deletions(-)
--
2.11.0
next reply other threads:[~2019-01-03 4:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 4:38 David Ahern [this message]
2019-01-03 4:38 ` [PATCH iproute2-next 1/5] libnetlink: Add filter function to rtnl_neighdump_req David Ahern
2019-01-03 4:38 ` [PATCH iproute2-next 2/5] ip neigh: Convert do_show_or_flush to use rtnl_neighdump_req David Ahern
2019-01-03 4:38 ` [PATCH iproute2-next 3/5] bridge: Update fdb show " David Ahern
2019-01-03 4:38 ` [PATCH iproute2-next 4/5] libnetlink: Add RTNL_HANDLE_F_STRICT_CHK flag David Ahern
2019-01-03 4:38 ` [PATCH iproute2-next 5/5] bridge: fdb: Fix filtering with strict checking disabled David Ahern
2019-01-04 13:45 ` Ido Schimmel
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=20190103043832.3748-1-dsahern@kernel.org \
--to=dsahern@kernel.org \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.