From: Benjamin Poirier <bpoirier@nvidia.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsahern@kernel.org>,
Stephen Hemminger <stephen@networkplumber.org>,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH iproute2 0/4] monitor command fixes
Date: Thu, 22 Sep 2022 15:19:34 +0900 [thread overview]
Message-ID: <20220922061938.202705-1-bpoirier@nvidia.com> (raw)
Fix problems in `bridge monitor` and `ip monitor` regarding the filtering
of object types and address families.
Benjamin Poirier (4):
bridge: Do not print stray prefixes in monitor mode
ip-monitor: Do not listen for nexthops by default when specifying
stats
ip-monitor: Include stats events in default and "all" cases
ip-monitor: Fix the selection of rtnl groups when listening for all
object types
bridge/br_common.h | 1 +
bridge/fdb.c | 3 ++
bridge/link.c | 4 ++
bridge/mdb.c | 3 ++
bridge/monitor.c | 35 ++++----------
bridge/vlan.c | 4 ++
bridge/vni.c | 4 ++
ip/ipmonitor.c | 115 +++++++++++++++++----------------------------
8 files changed, 71 insertions(+), 98 deletions(-)
--
2.37.2
next reply other threads:[~2022-09-22 6:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 6:19 Benjamin Poirier [this message]
2022-09-22 6:19 ` [PATCH iproute2 1/4] bridge: Do not print stray prefixes in monitor mode Benjamin Poirier
2022-09-22 15:28 ` Stephen Hemminger
2022-10-25 22:29 ` [PATCH iproute2] ip-monitor: Do not error out when RTNLGRP_STATS is not available Benjamin Poirier
2022-10-26 2:17 ` Stephen Hemminger
2022-10-26 3:20 ` Stephen Hemminger
2022-10-26 6:49 ` [PATCH iproute2 v2] " Benjamin Poirier
2022-09-22 6:19 ` [PATCH iproute2 2/4] ip-monitor: Do not listen for nexthops by default when specifying stats Benjamin Poirier
2022-09-22 6:19 ` [PATCH iproute2 3/4] ip-monitor: Include stats events in default and "all" cases Benjamin Poirier
2022-10-25 15:51 ` Stephen Hemminger
2022-09-22 6:19 ` [PATCH iproute2 4/4] ip-monitor: Fix the selection of rtnl groups when listening for all object types Benjamin Poirier
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=20220922061938.202705-1-bpoirier@nvidia.com \
--to=bpoirier@nvidia.com \
--cc=dsahern@kernel.org \
--cc=idosch@nvidia.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.