Backport of agent: remove data race in agent config into release/1.17.x #20203
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-consul-core
force-pushed
the
backport/rboyer/fix-agent-config-race/arguably-charming-mite
branch
from
ac50253 to
d3a0bd9
Compare
github-team-consul-core-pr-approver
approved these changes
Jan 12, 2024
rboyer
force-pushed
the
backport/rboyer/fix-agent-config-race/arguably-charming-mite
branch
from
d3a0bd9 to
052cc31
Compare
rboyer
deleted the
backport/rboyer/fix-agent-config-race/arguably-charming-mite
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport
This PR is auto-generated from #20200 to be assessed for backporting due to the inclusion of the label backport/1.17.
The below text is copied from the body of the original PR.
Description
To fix an issue displaying the current reloaded config in the
v1/agent/selfendpoint #18681 caused the agent's internalconfigstruct member to be deepcopied and replaced on reload.This is not safe because the field is not protected by a lock, nor should it be due to how it is accessed by the rest of the system.
This PR does the same deepcopy, but into a new field solely for the point of capturing the current reloaded values for display purposes. If there has been no reload then the original config is used.
Overview of commits