tcp/context: use mutex to avoid race condition when multiple operations are running #427
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.
When multiple operations are running we may end up calling
getPairfrom multiple threads simultaneously. This causes a crash due to duplicate connect calls and state modifications.This does add an additional synchronization point but under most usage this should be very cheap as after the first connection we only check a single variable and return.
Test plan:
pytorch/pytorch#150801