-
Notifications
You must be signed in to change notification settings - Fork 391
Refactor pkg mutex sites to use deferred unlocks consistently #33038
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
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
c1798fe
Initial plan
Copilot b926cf5
refactor mutex unlocks in pkg caches and logger
Copilot d2e08ff
refine deferred lock helpers in mcp cache
Copilot d7147b7
address review feedback on mutex refactor
Copilot 15c8a1e
Merge remote-tracking branch 'origin/main' into copilot/refactor-defe…
Copilot 535cef0
Merge remote-tracking branch 'origin/main' into copilot/refactor-defe…
Copilot d2071ce
Merge branch 'main' into copilot/refactor-defer-mu-unlock
pelikhan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
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.
[/improve-codebase-architecture] The
getPermissionEntry/deletePermissionEntryhelpers introduce a two-lock TOCTOU pattern: read under RLock, check expiry outside any lock, then conditionally delete under a new Lock. Between the two lock acquisitions, another goroutine could callSetPermission, inserting a fresh valid entry — whichdeletePermissionEntrywould then remove.This race existed before the refactor, but the helper split makes the two-phase pattern less visible. The original inline code at least co-located the two lock sites. Consider documenting the accepted race with a comment, or using
sync.Map/ a single write-lock forGetPermissionto close it definitively.