[FIXED] Avoid deadlock in updateAccountClaimsWithRefresh #6726
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.
Alternative fix for #6724, which could still deadlock.
Instead ensuring only one goroutine can go into this section in
updateAccountClaimsWithRefresh
which ensures we can't deadlock due to grabbing two account locks in succession.Have placed the server lock before the range over the accounts, but it could optionally be moved to be around the
acc.mu.Lock/Unlock
instead.Signed-off-by: Maurice van Veen [email protected]
Co-authored-by: Neil Twigg [email protected]