ipcache: fix possible data race in kvstore synchronizer #39369
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The blamed commit refactored the logic that synchronizes endpoint information into the kvstore to reduce the usage of globals. Yet, it still retrieved the kvstore client from the global accessor, pending its conversion to a proper cell. However, this turned out being affected by a data race, given that proper synchronization was not in place. Let's get this fixed by switching it to an atomic variable for the moment.
Fixes: f7e3eaa ("ipcache: inject kvstore synchronizer via Hive")
Fixes: #39294