-
Notifications
You must be signed in to change notification settings - Fork 111
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
Detect simultaneous borrow and drop of UnsafeCell #351
Open
e00E
wants to merge
1
commit into
tokio-rs:master
Choose a base branch
from
e00E:unsafecell_drop
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
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.
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.
Should
std::mem::needs_drop()
be used to solve this issue: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.
I don't agree with this.
Even if the inner type doesn't need to be dropped and thus its drop implementation does nothing, dropping the cell while a reference to the inner type exists is still wrong.
The documentation for needs_drop says that "this is purely an optimization hint". But we're changing observable behavior here. Using it would lead to safety assertions changing whether they get triggered based on the return value of needs_drop, which can change.
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.
Actually, this is isn't wrong to me. If an object is dropped, it means that all references pointing to it have reach the end of their lifetime, otherwise, the code wouldn't even compile.In fact, after thinking a second time about this sentence, it means that #349 is not an issue after all, and doesn't need to be "fixed".
My bad, the abstraction around
UnsafeCell
makes me forget that it was about pointers and not references.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.
This is an optimization hint, but the documentation still states "However if this function actually returns false, then you can be certain dropping T has no side effect". So
needs_drop
result is still guaranteed to have no false-negative, and can be relied on.Of course, as written in the documentation, it could lead to false-positives, but a few false positive may be still better than a too much conservative behavior leading to more false-positives. And if the result of
needs_drop
is changing with compiler versions, it's still guaranteed to not introduce false-negative.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.
Anyway, see my comment in the issue, I don't think loom is doing things right here. Dropping a cell should not be counted a mutable access but as a cell invalidation, for further
ConstPtr
/MutPtr
dereference.