[ptr] Fix soundness hole in "at least" invariants#909
Merged
Conversation
Previously, we spuriously implemented `at_least::Initialized` for the `Valid` invariant, which is unsound. This was introduced because, prior to the introduction of the `Initialized` invariant, all invariants were monotonic - when defined in the proper order, every invariant was at least as strict as all preceding invariants. Thus, the `define_system!` macro we use to define a system of invariants automatically emitted the appropriate impls based on this monotonicity assumption. `Initialized` broke this assumption, but we didn't update the macro to match. This commit changes the `define_system!` macro to require the caller to explicitly define the "at least" relation. It also adds a test to prevent regressions. As a consequence of making the "at least" relation explicit, we remove the `at_least::Initialized` trait, since this trait would have no non-trivial implementations.
jswrenn
approved these changes
Feb 18, 2024
dorryspears
pushed a commit
to dorryspears/zerocopy
that referenced
this pull request
Feb 20, 2024
Previously, we spuriously implemented `at_least::Initialized` for the `Valid` invariant, which is unsound. This was introduced because, prior to the introduction of the `Initialized` invariant, all invariants were monotonic - when defined in the proper order, every invariant was at least as strict as all preceding invariants. Thus, the `define_system!` macro we use to define a system of invariants automatically emitted the appropriate impls based on this monotonicity assumption. `Initialized` broke this assumption, but we didn't update the macro to match. This commit changes the `define_system!` macro to require the caller to explicitly define the "at least" relation. It also adds a test to prevent regressions. As a consequence of making the "at least" relation explicit, we remove the `at_least::Initialized` trait, since this trait would have no non-trivial implementations.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, we spuriously implemented
at_least::Initializedfor theValidinvariant, which is unsound. This was introduced because, prior to the introduction of theInitializedinvariant, all invariants were monotonic - when defined in the proper order, every invariant was at least as strict as all preceding invariants. Thus, thedefine_system!macro we use to define a system of invariants automatically emitted the appropriate impls based on this monotonicity assumption.Initializedbroke this assumption, but we didn't update the macro to match.This commit changes the
define_system!macro to require the caller to explicitly define the "at least" relation. It also adds a test to prevent regressions.As a consequence of making the "at least" relation explicit, we remove the
at_least::Initializedtrait, since this trait would have no non-trivial implementations.