Fix name lookup in PerformanceEntryReporter (use-after-free)#43646
Closed
tnovak wants to merge 1 commit into
Closed
Fix name lookup in PerformanceEntryReporter (use-after-free)#43646tnovak wants to merge 1 commit into
tnovak wants to merge 1 commit into
Conversation
Summary: PerformanceEntryReporter maintains a buffer of RawPerformanceEntry objects, as well as a set of _pointers_ to elements within that buffer, used to find entries by name. However, those pointers aren't stable: BoundedConsumableBuffer internally uses a vector, and there are a few cases where existing references get invalidated: - When the vector's capacity changes (as new entries get inserted) [1] - After calling clear-with-predicate, which copies elements into a new vector This causes nameLookup to contain dangling pointers, and subsequent operations on it can result in use-after-free. Fix this by having BoundedConsumableBuffer reserve space for maxSize entries up front (which ensures that existing pointers remain valid after adding new elements) and by rebuilding nameLookup after clearing entries by name. Note that reserve() causes the buffer's memory use to be higher than before in case where the number of elements is small relative to the max size. Given the (only) existing usage in PerformanceEntryReporter, as well as the property that consumed elements remain in the buffer, that cost should be minor. Changelog: [Internal] [1] https://en.cppreference.com/w/cpp/container/vector/push_back Reviewed By: rshest Differential Revision: D55273403
Contributor
|
This pull request was exported from Phabricator. Differential Revision: D55273403 |
Base commit: ac714b1 |
Contributor
|
This pull request has been merged in 5ea9471. |
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
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:
PerformanceEntryReporter maintains a buffer of RawPerformanceEntry objects,
as well as a set of pointers to elements within that buffer, used to find
entries by name.
However, those pointers aren't stable: BoundedConsumableBuffer internally uses
a vector, and there are a few cases where existing references get invalidated:
This causes nameLookup to contain dangling pointers, and subsequent operations
on it can result in use-after-free.
Fix this by having BoundedConsumableBuffer reserve space for maxSize entries
up front (which ensures that existing pointers remain valid after adding new
elements) and by rebuilding nameLookup after clearing entries by name.
Note that reserve() causes the buffer's memory use to be higher than before in
case where the number of elements is small relative to the max size. Given the
(only) existing usage in PerformanceEntryReporter, as well as the property that
consumed elements remain in the buffer, that cost should be minor.
Changelog: [Internal]
[1] https://en.cppreference.com/w/cpp/container/vector/push_back
Reviewed By: rshest
Differential Revision: D55273403