[QC-403] Protect pendingInfoRegions from concurrent access#4371
Merged
ktf merged 2 commits intoAliceO2Group:devfrom Sep 21, 2020
Merged
[QC-403] Protect pendingInfoRegions from concurrent access#4371ktf merged 2 commits intoAliceO2Group:devfrom
ktf merged 2 commits intoAliceO2Group:devfrom
Conversation
The callback which adds new elements to mPendingInfoRegions would be invoked in parallel if a device used both zeromq and shared memory transport.
knopers8
changed the title
Collaborator
Author
|
@ktf Could you please have a look? |
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
2 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.
The callback which adds new elements to mPendingInfoRegions would be invoked by FairMQ in parallel if a device used both zeromq and shared memory transport. As a result, proxies would sometimes crash during initialization.
As we register separate callbacks (one per channel) accessing the same resource, it seems fair to me that we take measures on the DPL side to avoid concurrent access.