diff options
| author | Donald Sharp <sharpd@nvidia.com> | 2022-01-28 11:17:53 -0500 |
|---|---|---|
| committer | Donald Sharp <sharpd@nvidia.com> | 2022-02-04 10:54:26 -0500 |
| commit | 2d51f27f028412ad089ff1f910f6489eb917631d (patch) | |
| tree | 0f7e43abd81a66868d7dfed4d325624f237ca209 /zebra/kernel_socket.c | |
| parent | 66a59f87435e5cb7be61a9566c3aecc8c3bcc5d7 (diff) | |
pimd: Only remove bsr NHT if we actually have tracked something
I'm now seeing in my log file:
2022/01/28 11:20:05 PIM: [Q0PZ7-QBBN3] attempting to delete nonexistent NHT BSR entry 0.0.0.0
2022/01/28 11:20:05 PIM: [Q0PZ7-QBBN3] attempting to delete nonexistent NHT BSR entry 0.0.0.0
2022/01/28 11:20:06 PIM: [Q0PZ7-QBBN3] attempting to delete nonexistent NHT BSR entry 0.0.0.0
When I run pimd. Looking at the code there are 3 places where pim_bsm.c removes the
NHT BSR tracking. In 2 of them the code ensures that the address is already setup
in 1 place it is not. Fix.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'zebra/kernel_socket.c')
0 files changed, 0 insertions, 0 deletions