diff options
author | Donald Sharp <sharpd@nvidia.com> | 2023-05-31 17:40:07 +0200 |
---|---|---|
committer | Donald Sharp <sharpd@nvidia.com> | 2023-06-01 13:35:12 +0200 |
commit | 82c6e4fea54eb65e153e6bc45bb718367b0b5132 (patch) | |
tree | cc0350a197a00e59356969162bf898ebda57751a /zebra/rib.h | |
parent | Merge pull request #13450 from patrasar/mld_core (diff) | |
download | frr-82c6e4fea54eb65e153e6bc45bb718367b0b5132.tar.xz frr-82c6e4fea54eb65e153e6bc45bb718367b0b5132.zip |
zebra: Unlock the route node when sending route notifications
When using a context to send route notifications to upper
level protocols, the code was using a locking function to
get the route node. There is no need for this to be locked
as such FRR should free it up.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'zebra/rib.h')
-rw-r--r-- | zebra/rib.h | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/zebra/rib.h b/zebra/rib.h index a56bb05d6..65cc1ffab 100644 --- a/zebra/rib.h +++ b/zebra/rib.h @@ -465,6 +465,13 @@ extern uint8_t route_distance(int type); extern void zebra_rib_evaluate_rn_nexthops(struct route_node *rn, uint32_t seq, bool rt_delete); +/* + * rib_find_rn_from_ctx + * + * Returns a lock increased route_node for the appropriate + * table and prefix specified by the context. Developer + * should unlock the node when done. + */ extern struct route_node * rib_find_rn_from_ctx(const struct zebra_dplane_ctx *ctx); |