feat!: move kernel MMR position to u64
#5956
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.
Description
Switches the handling of kernel MMR positions from
u32
tou64
.Closes #5924.
Motivation and Context
Internally, MMR positions are handled as either
usize
oru64
. However, they are eventually parsed and handled asu32
for storage. While it doesn't address the internalusize
handling, it switches storage operations to beu64
.How Has This Been Tested?
Existing tests pass.
What process can a PR reviewer use to test or verify this change?
Assert that the logic, especially around LMDB operations, is correct.
BREAKING CHANGE: Modifies the handling of kernel MMR data in LMDB.