Safety improvements for repr(stabby)
enums
#69
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.
ABI BREAKING CHANGE
While
stabby::result::Result
's actual layout hasn't truly changed, this PR fixes a soundness hole which might still be triggered by exploiting aResult
received from a binary with the previous representation.stabby
treats this release'sResult
as different from that of the previous.Fixing an unsoundness in
stabby::result::Result
which infected allrepr(stabby)
enumstabby::result::Result
sometimes encodes determinants in structure padding. However, until this PR, rustc was free to treat these paddings as unused data, making reads in these regions UB.Due to this, any
repr(stabby)
enum that used these determinants is unsound until this PR is merged.This PR addresses this by ensure Rust treats enums as a blob of memory with the appropriate size and alignment.
A nice side effect of this PR is that Rust previously treated
repr(stabby)
enums asimproper_ctypes
due to the determinants being ZSTs, as highlighted by issue #68. This is no longer the case.