Limit async stream read/write lengths#1588
Merged
alexcrichton merged 1 commit intoApr 14, 2026
Merged
Conversation
The canonical ABI requires that the maximum size of any one stream operation is `(1 << 28) - 1`, so this commit places that limit on the runtime implementation. This generally isn't applicable but it does get used for `stream` without a payload where otherwise the capacity of vectors is `usize::MAX`, hence large reads/writes.
dicej
approved these changes
Apr 14, 2026
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
2 participants
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 canonical ABI requires that the maximum size of any one stream operation is
(1 << 28) - 1, so this commit places that limit on the runtime implementation. This generally isn't applicable but it does get used forstreamwithout a payload where otherwise the capacity of vectors isusize::MAX, hence large reads/writes.