netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joachim Wiberg <troglobit@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Nikolay Aleksandrov <razor@blackwall.org>,
	Roopa Prabhu <roopa@nvidia.com>,
	netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
	"David S . Miller" <davem@davemloft.net>,
	Joachim Wiberg <troglobit@gmail.com>
Subject: [PATCH v2 net-next 0/2] net: bridge: add support for host l2 mdb entries
Date: Mon, 11 Apr 2022 10:40:52 +0200	[thread overview]
Message-ID: <20220411084054.298807-1-troglobit@gmail.com> (raw)
In-Reply-To: <20220223172407.175865-1-troglobit@gmail.com>

Fix to an obvious omissions for layer-2 host mdb entries, this v2 adds
the missing selftest and some minor style fixes.

Note: this patch revealed some worrying problems in how the bridge
      forwards unknown BUM traffic and also how unknown multicast is
      forwarded when a IP multicast router is known, which a another
      (RFC) patch series intend to address.  That series will build
      on this selftest, hence the name of the test.

 /Joachim

v2:
  - Add braces to other if/else clauses (Jakub)
  - Add selftest to verify add/del of mac/ipv4/ipv6 mdb entries (Jakub)

Joachim Wiberg (2):
  net: bridge: add support for host l2 mdb entries
  selftests: forwarding: new test, verify host mdb entries

 net/bridge/br_mdb.c                           |  12 +-
 .../testing/selftests/net/forwarding/Makefile |   1 +
 .../selftests/net/forwarding/bridge_mdb.sh    | 103 ++++++++++++++++++
 3 files changed, 111 insertions(+), 5 deletions(-)
 create mode 100755 tools/testing/selftests/net/forwarding/bridge_mdb.sh

-- 
2.25.1


  parent reply	other threads:[~2022-04-11  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 17:24 [PATCH 1/1 net-next] net: bridge: add support for host l2 mdb entries Joachim Wiberg
2022-02-24 11:26 ` Nikolay Aleksandrov
2022-02-24 13:59   ` Joachim Wiberg
2022-02-24 16:06   ` Jakub Kicinski
2022-02-24 16:29     ` Joachim Wiberg
2022-02-24 16:48       ` Jakub Kicinski
2022-02-24 17:27         ` Joachim Wiberg
2022-04-11  8:40 ` Joachim Wiberg [this message]
2022-04-11  8:40   ` [PATCH v2 net-next 1/2] " Joachim Wiberg
2022-04-11  8:40   ` [PATCH v2 net-next 2/2] selftests: forwarding: new test, verify host " Joachim Wiberg
2022-04-12  8:30   ` [PATCH v2 net-next 0/2] net: bridge: add support for host l2 " patchwork-bot+netdevbpf

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=20220411084054.298807-1-troglobit@gmail.com \
    --to=troglobit@gmail.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.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).