Mutex::unlock - decrement _count inside lock #12983
Merged
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.
Summary of changes
Mutex::unlock
was decrementing the_count
member after releasing the mutex, which meant it was unprotected, exposing a race that could corrupt the count.This could lead to an assert in
ConditionVariable::wait
, which checks that the mutex count is one.Fixes #12976. Bug was introduced in #10358 (5.13 and 5.12.2).
Impact of changes
Migration actions required
Documentation
None
Pull request type
Test results
Reviewers
@AriParkkila, @evedon