0-initialize thread-specific data upon thread creation. #508
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
If thread-specific data is not set to 0 upon thread creation, `__pthread_tsd_run_dtors` will end up running destructors passing uninitialized memory as memory addresses, which can lead to memory corruption. This issue can be triggered when malloc() returns a memory address that was freed before, as in that case memory is not zeroed out.
abrown
approved these changes
Jul 3, 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.
If thread-specific data is not set to 0 upon thread creation,
__pthread_tsd_run_dtorswill end up running destructors passing uninitialized memory as memory addresses, which can lead to memory corruption.This issue can be triggered when malloc() returns a memory address that was freed before, as in that case memory is not zeroed out.