Fix potential deadlock in GetByListener function#489
Open
roosenj wants to merge 1 commit intomochi-mqtt:mainfrom
Open
Fix potential deadlock in GetByListener function#489roosenj wants to merge 1 commit intomochi-mqtt:mainfrom
GetByListener function#489roosenj wants to merge 1 commit intomochi-mqtt:mainfrom
Conversation
The deadlock occured when a write lock was requested between the two recursive read locks. The second read lock request blocked, preventing the first read lock from releasing and allowing the write lock, thus creating a deadlock.
IshanDaga
previously approved these changes
Apr 11, 2026
roosenj
force-pushed
the
bug/recursive-read-deadlock
branch
from
4e7a939 to
57237dd
Compare
Author
|
seems I pushed our gitlab CI configuration by accident, so I've removed it |
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
6 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 deadlock occured when a write lock was requested between the two recursive read locks. The second read lock request blocked, preventing the first read lock from releasing and allowing the write lock, thus creating a deadlock.
This fixes issue #488