diff options
| author | plsaranya <saranya_panjarathina@dell.com> | 2022-03-23 19:16:46 +0530 |
|---|---|---|
| committer | plsaranya <saranya_panjarathina@dell.com> | 2022-03-25 19:48:54 +0530 |
| commit | db89f2a3ebd29b53fc06e2c6735b6ff0ff9dcf8a (patch) | |
| tree | d4fe7daf99d202721abdde5f86995f5f06aa269b /pimd/pim_upstream.c | |
| parent | 52093e0f0e5753b753ae1b048f69b979ed3c75f6 (diff) | |
pimd: Assert fixes
Problem:
PIM assert is not triggered even after receiving WRONGVIF notification because of Could_assert flag not set.
CouldAssert(S,G,I) =
SPTbit(S,G)==TRUE
AND (RPF_interface(S) != I)
AND (I in ( ( joins(*,G) (-) prunes(S,G,rpt) )
(+) ( pim_include(*,G) (-) pim_exclude(S,G) )
(-) lost_assert(*,G)
(+) joins(S,G) (+) pim_include(S,G) ) )
Once SPTbit is set, Could_assert has to be reevaluated
Signed-off-by: plsaranya <Saranya_Panjarathina@dell.com>
Diffstat (limited to 'pimd/pim_upstream.c')
| -rw-r--r-- | pimd/pim_upstream.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/pimd/pim_upstream.c b/pimd/pim_upstream.c index 571117ac0a..70f16d066a 100644 --- a/pimd/pim_upstream.c +++ b/pimd/pim_upstream.c @@ -2062,6 +2062,7 @@ static bool pim_upstream_sg_running_proc(struct pim_upstream *up) if ((up->sptbit != PIM_UPSTREAM_SPTBIT_TRUE) && (up->rpf.source_nexthop.interface)) { pim_upstream_set_sptbit(up, up->rpf.source_nexthop.interface); + pim_upstream_update_could_assert(up); } return rv; |