From: Ido Schimmel <idosch@nvidia.com>
To: netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, roopa@nvidia.com, razor@blackwall.org,
mlxsw@nvidia.com, Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next v2 07/14] bridge: mcast: Add a flag for user installed source entries
Date: Sat, 10 Dec 2022 16:56:26 +0200 [thread overview]
Message-ID: <20221210145633.1328511-8-idosch@nvidia.com> (raw)
In-Reply-To: <20221210145633.1328511-1-idosch@nvidia.com>
There are a few places where the bridge driver differentiates between
(S, G) entries installed by the kernel (in response to Membership
Reports) and those installed by user space. One of them is when deleting
an (S, G) entry corresponding to a source entry that is being deleted.
While user space cannot currently add a source entry to a (*, G), it can
add an (S, G) entry that later corresponds to a source entry created by
the reception of a Membership Report. If this source entry is later
deleted because its source timer expired or because the (*, G) entry is
being deleted, the bridge driver will not delete the corresponding (S,
G) entry if it was added by user space as permanent.
This is going to be a problem when the ability to install a (*, G) with
a source list is exposed to user space. In this case, when user space
installs the (*, G) as permanent, then all the (S, G) entries
corresponding to its source list will also be installed as permanent.
When user space deletes the (*, G), all the source entries will be
deleted and the expectation is that the corresponding (S, G) entries
will be deleted as well.
Solve this by introducing a new source entry flag denoting that the
entry was installed by user space. When the entry is deleted, delete the
corresponding (S, G) entry even if it was installed by user space as
permanent, as the flag tells us that it was installed in response to the
source entry being created.
The flag will be set in a subsequent patch where source entries are
created in response to user requests.
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
---
net/bridge/br_multicast.c | 3 ++-
net/bridge/br_private.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/net/bridge/br_multicast.c b/net/bridge/br_multicast.c
index 8432b4ea7f28..48170bd3785e 100644
--- a/net/bridge/br_multicast.c
+++ b/net/bridge/br_multicast.c
@@ -552,7 +552,8 @@ static void br_multicast_fwd_src_remove(struct net_bridge_group_src *src,
continue;
if (p->rt_protocol != RTPROT_KERNEL &&
- (p->flags & MDB_PG_FLAGS_PERMANENT))
+ (p->flags & MDB_PG_FLAGS_PERMANENT) &&
+ !(src->flags & BR_SGRP_F_USER_ADDED))
break;
if (fastleave)
diff --git a/net/bridge/br_private.h b/net/bridge/br_private.h
index a3db99d79a3d..74f17b56c9eb 100644
--- a/net/bridge/br_private.h
+++ b/net/bridge/br_private.h
@@ -300,6 +300,7 @@ struct net_bridge_fdb_flush_desc {
#define BR_SGRP_F_DELETE BIT(0)
#define BR_SGRP_F_SEND BIT(1)
#define BR_SGRP_F_INSTALLED BIT(2)
+#define BR_SGRP_F_USER_ADDED BIT(3)
struct net_bridge_mcast_gc {
struct hlist_node gc_node;
--
2.37.3
next prev parent reply other threads:[~2022-12-10 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 14:56 [PATCH net-next v2 00/14] bridge: mcast: Extensions for EVPN Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 01/14] bridge: mcast: Do not derive entry type from its filter mode Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 02/14] bridge: mcast: Split (*, G) and (S, G) addition into different functions Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 03/14] bridge: mcast: Place netlink policy before validation functions Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 04/14] bridge: mcast: Add a centralized error path Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 05/14] bridge: mcast: Expose br_multicast_new_group_src() Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 06/14] bridge: mcast: Expose __br_multicast_del_group_src() Ido Schimmel
2022-12-10 14:56 ` Ido Schimmel [this message]
2022-12-10 14:56 ` [PATCH net-next v2 08/14] bridge: mcast: Avoid arming group timer when (S, G) corresponds to a source Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 09/14] bridge: mcast: Add support for (*, G) with a source list and filter mode Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 10/14] bridge: mcast: Allow user space to add " Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 11/14] bridge: mcast: Allow user space to specify MDB entry routing protocol Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 12/14] bridge: mcast: Support replacement of MDB port group entries Ido Schimmel
2022-12-11 9:26 ` Nikolay Aleksandrov
2022-12-10 14:56 ` [PATCH net-next v2 13/14] selftests: forwarding: Rename bridge_mdb test Ido Schimmel
2022-12-10 14:56 ` [PATCH net-next v2 14/14] selftests: forwarding: Add bridge MDB test Ido Schimmel
2022-12-12 23:40 ` [PATCH net-next v2 00/14] bridge: mcast: Extensions for EVPN 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=20221210145633.1328511-8-idosch@nvidia.com \
--to=idosch@nvidia.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).