[Storage] Fix CRC64 extension with large data #39655
Merged
Conversation
This file contains 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
jalauzon-msft
requested review from
annatisch,
vincenttran-msft and
weirongw23-msft
as code owners
weirongw23-msft
approved these changes
Feb 11, 2025
kyleknap
approved these changes
Feb 11, 2025
vincenttran-msft
approved these changes
Feb 12, 2025
|
/check-enforcer evaluate |
|
/azp run python - pullrequest |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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.
The Storage extensions CRC64 calculation could be incorrect when computing the CRC over large data (> 2GiB). This was likely caused by integer overflow as there was one variable used in the calculation that was an
intinstead ofuint64_twhich this PR fixes. This has been manually tested.