[Apple] Lock over the same object in SafeDeleteSslContext to serialize access to the buffers #117982
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.
Description
OSX SafeDeleteSslContext takes lock on different object in managed callbacks and other methods. In the callbacks, the lock is SafeDeleteSslContext, while in Dispose and other methods the lock is SafeSslHandle.
This PR adds a
_lock
to ensure synchronization across all methods that access shared buffers. The issue was identified while working on #117950.