Clean up an invalid memory access in makeCSR() #463
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.
The pointer variant of
makeCSR()
can read past the end of thepos
array. In some (rare, unlucky) cases, this can cause the program to segfault.The issue is that
TypedComponentRef::getAsIndex
does two 64-bit reads (of a 128-bit union type) and then passes (by value) down to the accessor method. The solution is to pass a reference instead, so the accessor method only does a 32-bit read, and does not touch the other memory locations.I also added a test case that carefully arranges memory to guarantee that out-of-bounds accesses will segfault.
Fixes: #455
Here's what valgrind says before the patch was applied:
And after applying the patch: