diff options
| author | Jafar Al-Gharaibeh <jafar@atcorp.com> | 2024-05-30 12:46:47 -0500 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2024-05-31 14:58:54 +0000 |
| commit | 9101a9f6e9aa0a7e9c4c81a15574d60b84ec9d77 (patch) | |
| tree | b2546db59bb96bc0ad6f1d9a355b08ec6cf5682d /lib/lib_errors.c | |
| parent | d19d021b53c15160bd241c56124e5218d64ebccc (diff) | |
pimd: fix crash when mixing ssm/any-source joins
There is no reason to call `igmp_anysource_forward_stop()` inside a call to
`igmp_get_source_by_addr()`; not only it is not expected for a "get" function
to perform such an action, but also the decision to start/stop forwarding is
already handled correctly by pim outside `igmp_get_source_by_addr()`.
That call was left there from the days pim was initially imported into the sources.
The problem/crash was happening because `igmp_find_source_by_addr()` would fail to
find the group/source combo when mixing `(*, G)` and `(S, G)`. When having an existing
flow `(*, G)`, and a new `(S, G)` igmp is received, a new entry is correctly created.
`igmp_anysource_forward_stop(group)` always stops and eventually frees `(*, G)`, even
when the new igmp is `(S, G)`, leaving a bad state. I.e, the new entry for `(S, G)`
causes `(*, G)` to be deleted.
Tested the fix with multiple receivers on the same interface with several ssm and
any source senders and receivers with various combination of start/stop orders and
they all worked correctly.
Fixes: #15630
Signed-off-by: Jafar Al-Gharaibeh <jafar@atcorp.com>
(cherry picked from commit a951960a15e8b6b5ed248abb0ecc9eb4e9a3427f)
Diffstat (limited to 'lib/lib_errors.c')
0 files changed, 0 insertions, 0 deletions
