The dg_update_list access is controlled by the dg_mutex in all
other locations. Let's just add a mutex usage around the initialization
of the dg_update_list even if it's part of the startup, just to keep
things consistent.
Signed-off-by: Donald Sharp <sharpd@nvidia.com>
(cherry picked from commit
19af3f3d7af0f8904794dae3c36f60ed1d5a3cc8)
dplane_prov_list_init(&zdplane_info.dg_providers);
- dplane_ctx_list_init(&zdplane_info.dg_update_list);
+ frr_with_mutex (&zdplane_info.dg_mutex) {
+ dplane_ctx_list_init(&zdplane_info.dg_update_list);
+ }
+
zns_info_list_init(&zdplane_info.dg_zns_list);
zdplane_info.dg_updates_per_cycle = DPLANE_DEFAULT_NEW_WORK;