-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use AtomicPtr instead of AtomicUsize for Weak #263
Merged
Merged
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
This allows Strict Provenance to work properly, fixing #262. It also now matches what `libstd` does: https://github.com/rust-lang/rust/blob/9f7e997c8bc3cacd2ab4eb75e63cb5fa9279c7b0/library/std/src/sys/unix/weak.rs#L85-L141 Also, while reading the `libstd` code, I noticed that they use an `Acquire` fence and `Release` store as the returned pointer should have "consume" semantics. I changed our code to do something slightly stronger (Acquire load and Release store) for consistancy. Signed-off-by: Joe Richey <joerichey@google.com>
CC @nvzqz if you want to take a look. |
josephlr
force-pushed
the
strict_prov
branch
2 times, most recently
from
June 7, 2022 07:53
214a4a2
to
0498e88
Compare
Signed-off-by: Joe Richey <joerichey@google.com>
nvzqz
approved these changes
Jun 7, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this! Using [patch.crates-io]
in my Cargo.toml
, I was able to verify that this makes my code's tests now pass under strict provenance.
fbstj
reviewed
Jun 7, 2022
newpavlov
approved these changes
Jun 7, 2022
Co-authored-by: Joe ST <joe@fbstj.net>
This means: - Relaxed Load - Release Store - Acquire fence when returning pointer Signed-off-by: Joe Richey <joerichey@google.com>
josephlr
force-pushed
the
strict_prov
branch
2 times, most recently
from
June 9, 2022 05:31
2085d7d
to
0b03f3d
Compare
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.
Fixes #262
This allows Strict Provenance to work properly. It also now matches what
libstd
does:https://github.com/rust-lang/rust/blob/9f7e997c8bc3cacd2ab4eb75e63cb5fa9279c7b0/library/std/src/sys/unix/weak.rs#L85-L141
Also, while reading the
libstd
code, I noticed that they use anAcquire
fence andRelease
store as the returned pointer should have "consume" semantics. I changed our code to do something slightly stronger (Acquire load and Release store) as it's simpler and definitely correct.Signed-off-by: Joe Richey joerichey@google.com