summaryrefslogtreecommitdiff
path: root/pimd/pim_instance.h
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@nvidia.com>2021-05-12 14:31:45 -0400
committerDonald Sharp <sharpd@nvidia.com>2021-05-12 14:36:59 -0400
commitd3cc1e45182196a0b9b7146bcbaef04f346d9721 (patch)
tree2841feca90eae72f58a1c0c3e23af860db3f3b46 /pimd/pim_instance.h
parente5981db7e9eda027c189d3d528f7e02c05faf29a (diff)
pimd: Remove pim->vrf_id and use pim->vrf->vrf_id
VRF creation can happen from either cli or from knowledged about the vrf learned from zebra. In the case where we learn about the vrf from the cli, the vrf id is UNKNOWN. Upon actual creation of the vrf, lib/vrf.c touches up the vrf_id and calls pim_vrf_enable to turn it on properly. At this point in time we have a pim->vrf_id of UNKNOWN and the vrf->vrf_id of the right value. There is no point in duplicating this data. So just remove all pim->vrf_id and use the vrf->vrf_id instead since we keep a copy of the pim->vrf pointer. This will remove some crashes where we expect the pim->vrf_id to be usable and it's not. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
Diffstat (limited to 'pimd/pim_instance.h')
-rw-r--r--pimd/pim_instance.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/pimd/pim_instance.h b/pimd/pim_instance.h
index 2b76da21b2..72c726690c 100644
--- a/pimd/pim_instance.h
+++ b/pimd/pim_instance.h
@@ -127,7 +127,7 @@ struct pim_router {
/* Per VRF PIM DB */
struct pim_instance {
- vrf_id_t vrf_id;
+ // vrf_id_t vrf_id;
struct vrf *vrf;
struct {