diff options
author | Nikolay Aleksandrov <nikolay@nvidia.com> | 2020-09-22 10:30:24 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-09-23 13:24:34 -0700 |
commit | 8266a0491e92d39dc9af739e8380a0daa9b8836b (patch) | |
tree | 4dca1a636387dba3de2bd91d58132ed27da1450d /arch/powerpc/lib | |
parent | b08123684bd55fa6d6ee4b52d4ae3040fadb5aa2 (diff) | |
download | linux-8266a0491e92d39dc9af739e8380a0daa9b8836b.tar.bz2 |
net: bridge: mcast: handle port group filter modes
We need to handle group filter mode transitions and initial state.
To change a port group's INCLUDE -> EXCLUDE mode (or when we have added
a new port group in EXCLUDE mode) we need to add that port to all of
*,G ports' S,G entries for proper replication. When the EXCLUDE state is
changed from IGMPv3 report, br_multicast_fwd_filter_exclude() must be
called after the source list processing because the assumption is that
all of the group's S,G entries will be created before transitioning to
EXCLUDE mode, i.e. most importantly its blocked entries will already be
added so it will not get automatically added to them.
The transition EXCLUDE -> INCLUDE happens only when a port group timer
expires, it requires us to remove that port from all of *,G ports' S,G
entries where it was automatically added previously.
Finally when we are adding a new S,G entry we must add all of *,G's
EXCLUDE ports to it.
In order to distinguish automatically added *,G EXCLUDE ports we have a
new port group flag - MDB_PG_FLAGS_STAR_EXCL.
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'arch/powerpc/lib')
0 files changed, 0 insertions, 0 deletions