[mod_sofia] Fixing deadlock in issue #2290 #2387
Open
+3
−0
Conversation
This file contains 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
…ING_NECESSARY that we should be following this code path, but it does not look like there's anything that gets changed when we enter sofia_receive_message() in this case. Thus there's no sense in locking tech_pvt->sofia_mutex , thus avoiding the deadlock described in issue signalwire#2290.
bferreirq
approved these changes
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I cannot certify that on SWITCH_MESSAGE_INDICATE_TRANSCODING_NECESSARY that we should be following this code path, but it does not look like there's anything that gets changed when we enter sofia_receive_message() in this case. Thus there's no sense in locking tech_pvt->sofia_mutex , thus avoiding the deadlock described in issue #2290.