New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: race condition in lockMap #2985
fix: race condition in lockMap #2985
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andyzhangx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-cloud-provide-azure canceled.
|
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. I thought race conditions should have already been covered since 'go test -race' is already running. Thanks for adding a new race condition test.
/lgtm |
What type of PR is this?
/kind bug
What this PR does / why we need it:
fix: race condition in lockMap
lm.Lock()
is intended for lockinglm.mutexMap
, while original logic inLockEntry
does not locklm.mutexMap
well, inlm.lockEntry(entry)
, it's still accessinglm.mutexMap
outside oflm.Lock()
...lm.Unlock()
This PR removes
addEntry
func invoke, makelm.mutexMap
access inside oflm.Lock()
...lm.Unlock()
, and then lock ougside.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
go test -race
:Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: