[v1.19] ipam: Use existing mutex for multipool capacity synchronization#44777
Merged
julianwiedmann merged 1 commit intov1.19from Mar 16, 2026
Merged
Conversation
The backport conflict resolution incorrectly introduced a new poolsMutex that isn't used anywhere else, hence providing no actual synchronization. Use the existing m.mutex instead, matching the upstream fix. Fixes: db32834 ("ipam: Fix concurrent map access to multipool map") Fixes: #44517 Reported-by: Marco Iorio <marco.iorio@isovalent.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
Member
Author
|
/test |
21 tasks
joestringer
approved these changes
Mar 13, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Directly fixing incorrect backport from #44517.
Reported-by: @giorio94 in #44517 (comment)