cord_lc: Process truncated reads [backport 2024.01]#20552
Merged
maribu merged 1 commit intoRIOT-OS:2024.01-branchfrom Apr 8, 2024
Merged
cord_lc: Process truncated reads [backport 2024.01]#20552maribu merged 1 commit intoRIOT-OS:2024.01-branchfrom
maribu merged 1 commit intoRIOT-OS:2024.01-branchfrom
Conversation
Co-Authored-By: Marian Buschsieweke <[email protected]> (cherry picked from commit 9820a65)
chrysn
approved these changes
Apr 8, 2024
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.
Backport of #20547
Contribution description
When a Resource Directory reports overly long .well-known/core results, those might be truncated due to a limited buffer. This PR ensures that the parts that are received are processed.
It also removes zeroing of the buffer -- clif does not require C style string termination.
Testing procedure
Issues/PRs references
@maribu provided the original version of this.
@Teufelchen1, can this still go in?