multi: avoid reading whole struct pointer from pointer #15063
Closed
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
The proper alignment is not guaranteed. This now uses only the first and last byte in the key since they are the ones likely to change most (one of them, depending on CPU endian) and the hash is tiny anyway.
bagder
changed the title
|
Analysis of PR #15063 at 7afd6417: Test 2405 failed, which has NOT been flaky recently, so there could be a real issue in the PR. Test 1035 failed, which has NOT been flaky recently, so there could be a real issue in the PR. Generated by Testclutch |
|
if the keylen is greater than the size of a Curl_easy then wouldn't it be out of bounds? |
|
They keys are |
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 proper alignment is not guaranteed. This now uses only the first and last byte in the key since they are the ones likely to change most (one of them, depending on CPU endian) and the hash is tiny anyway.