Correct EOF handling in stream read in ChaChaDualPolyReadAdapter
#4144
+20
−1
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.
When
ChaChaDualPolyReadAdapter
encounters an EOF (Read::read
returnsOk(0)
) while trying to drain the stream (even though theFixedLengthReader
thinks it has available space) we'll end up infinite-looping trying to drain the stream looking forRead::read
to return anErr
(which it won't).The fix is, of course, simple, to detect the EOF signal.
Found by the
onion_message_target
fuzzer which @dergoegge ran. Thanks to @morehouse for digging deeper on the specific fuzz test case and thoroughly reporting the underlying causes.Fixes #4139.