Avoid two panics during parsing #128
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 first occurs when checking the length of RouteNextHopBuffer.
If the next-hops length is u16::MAX, adding 8 (the PAYLOAD_OFFSET) to
it would cause integer overflow and lead to a panic. Rather than
switching to
saturating_add, remove the addition entirely. It wasunnecessary, as the provided length already accounts for the RTA struct.
The second occurs when parsing a TcU32Selector.
TcU32SelectorBuffer::new_checkedreturns an error when the underlyingbuffer is not large enough to contain
nkeys. This avoids anindex-out-of-bounds panic in
TcU32Selector::parse, when extractingkeys from the underlying buffer.