Make export::acquire() and export::release() unsafe#659
Merged
bors[bot] merged 3 commits intoknurling-rs:mainfrom Feb 15, 2022
Merged
Make export::acquire() and export::release() unsafe#659bors[bot] merged 3 commits intoknurling-rs:mainfrom
bors[bot] merged 3 commits intoknurling-rs:mainfrom
Conversation
Calling export::release() may enable interrupts, which is unsound if done inside a critical section or other code which expects interrupts to be disabled. Calling export::acquire() is less dangerous (no obvious way to cause unsoundness), but is still a bad idea and breaks the safety contract of critical_section::acquire(), which must only be called paired with critical_section::release().
Member
|
Thank you! bors r+ |
Contributor
|
Build succeeded: |
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.
Calling export::release() may enable interrupts, which is unsound
if done inside a critical section or other code which expects interrupts
to be disabled.
Calling export::acquire() is less dangerous (no obvious way to cause
unsoundness), but is still a bad idea and breaks the safety contract
of critical_section::acquire(), which must only be called paired with
critical_section::release().