-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix #5808: Handle possible dangling reference safely #5812
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
matheus-consoli
force-pushed
the
5808-maybedangling
branch
from
June 23, 2023 00:09
66b3679
to
ed19ce8
Compare
Darksonn
added
A-tokio-util
Area: The tokio-util crate
M-sync
Module: tokio/sync
labels
Jun 23, 2023
Darksonn
reviewed
Jun 23, 2023
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.
Thank you for the PR.
matheus-consoli
changed the title
Fix #5080: Handle possible dangling reference safely
Fix #5008: Handle possible dangling reference safely
Jun 24, 2023
matheus-consoli
changed the title
Fix #5008: Handle possible dangling reference safely
Fix #5808: Handle possible dangling reference safely
Jun 24, 2023
Darksonn
reviewed
Jun 25, 2023
Darksonn
reviewed
Jun 25, 2023
matheus-consoli
force-pushed
the
5808-maybedangling
branch
2 times, most recently
from
June 27, 2023 21:17
9c61198
to
eac9b92
Compare
matheus-consoli
force-pushed
the
5808-maybedangling
branch
from
June 27, 2023 21:38
eac9b92
to
996a742
Compare
Darksonn
approved these changes
Jun 28, 2023
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. Looks good to me.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Attempts to fix #5808.
Motivation
Handle
Notify
as a possible dangling reference to avoid Undefined Behavior.Technically, this is not UB today because
Notify
uses anUnsafeCell
internally, which prevents the problem with the pointer aliasing rules based on https://doc.rust-lang.org/stable/reference/behavior-considered-undefined.html.Solution
Wrap the reference holder with a
MaybeUninit
.