Avoid squirrelly memcpy()
call in filesystem.cpp
#4933
Merged
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.
We have an extremely squirrelly line of code that's
memcpy
ing two consecutiveDWORD
s into the beginning of a buffer. There's no reason for this weirdness - it isn't perf-critical, and the optimizer should understandmemcpy
. Now, code analysis tools (specifically CodeQL) are noticing that this code is a 🐿️ read overrun. Let's avoid this by splitting it up into two separate reads.For the destination,
_Id
points toFILE_ID_INFO
. ItsFileId
isFILE_ID_128
, which containsBYTE Identifier[16];
.For the source,
_Info
isBY_HANDLE_FILE_INFORMATION
: