py/stream: Check for stream read function returning too many bytes. #13572
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.
Closes #13046. This is two fixes:
mp_vfs_blockdev_read_ext/mp_vfs_blockdev_write_ext
to be 0 or a negative integer. Returning positive integers here confuses littlefs (see lfs1.c:66 for example) and led to the linked bug. In general it seems like it can lead to unexpected behaviour, in libraries not part of MicroPython.Either one of these is sufficient to fix the linked issue, but checking both seem potentially worthwhile as it's possible for other similar cases to arise (either different stream implementations that return the wrong length, or other errors in block device consumers that are returned invalid results.)
This work was funded through GitHub Sponsors.