diff options
| author | Nikolay Aleksandrov <nikolay@nvidia.com> | 2021-10-29 15:05:27 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-11-18 21:16:44 +0300 |
| commit | bbf7b2dbd131f6dc025cfd84fedae73bead8e50a (patch) | |
| tree | 73bddfcba352d60104b064594355c6955f0d6908 /crypto | |
| parent | 24c8fd323957d80521caefa2b2f5a67531cf2ec1 (diff) | |
| download | linux-bbf7b2dbd131f6dc025cfd84fedae73bead8e50a.tar.xz | |
selftests: net: bridge: update IGMP/MLD membership interval value
[ Upstream commit 34d7ecb3d4f772eb00ce1f7195ae30886ddf4d2e ]
When I fixed IGMPv3/MLDv2 to use the bridge's multicast_membership_interval
value which is chosen by user-space instead of calculating it based on
multicast_query_interval and multicast_query_response_interval I forgot
to update the selftests relying on that behaviour. Now we have to
manually set the expected GMI value to perform the tests correctly and get
proper results (similar to IGMPv2 behaviour).
Fixes: fac3cb82a54a ("net: bridge: mcast: use multicast_membership_interval for IGMPv3")
Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions