payload_update: Round up erase size to 4KB sector boundary for binay files - #298
Merged
Merged
Conversation
stevenportley
approved these changes
Sep 17, 2026
… files When binary_file is true (--binary), round the erase length in libhoth_payload_update up to the next 4 KiB sector boundary before calling libhoth_payload_update_erase, while checking for uint32_t overflow. Signed-off-by: Christian Kungler <ckungler@google.com>
ckungler
force-pushed
the
binary_erase_round_up
branch
from
September 17, 2026 20:54
301d8b1 to
fc706fd
Compare
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.
When binary_file is true (--binary), round the erase length in libhoth_payload_update up to the next 4 KiB sector boundary before calling libhoth_payload_update_erase, while checking for uint32_t overflow.