config: acquire write lock when overwriting the map #92606
Merged
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
Previously, by mistake we were acquiring a read lock even though we do write operations in `PurgeZoneConfigCache`. Release note: None
|
Also, Mark, it looks like #87391 wasn't backported, right? |
|
This change is |
|
TFTR! bors r+ |
|
Build failed (retrying...): |
|
Build succeeded: |
msirek
reviewed
Nov 29, 2022
There was a problem hiding this comment.
Also, Mark, it looks like #87391 wasn't backported, right?
That's right.
Reviewable status:
complete! 0 of 0 LGTMs obtained
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.
Previously, by mistake we were acquiring a read lock even though we do write operations in
PurgeZoneConfigCache.Fixes: #92519.
Release note: None