Skip to content
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 unsafe pointers for values that the kernel may update behind our backs #23

Merged
merged 1 commit into from
May 6, 2020

Conversation

spacejam
Copy link
Owner

@spacejam spacejam commented May 6, 2020

No description provided.

@CLAassistant
Copy link

CLAassistant commented May 6, 2020

CLA assistant check
All committers have signed the CLA.

@spacejam spacejam merged commit 5415ddb into master May 6, 2020
@spacejam spacejam deleted the tyler_0.9.3 branch May 6, 2020 17:20
Comment on lines +33 to +38
/// # Safety
///
/// Never call `std::mem::forget` on this value.
/// It can lead to a use-after-free bug. The fact
/// that `std::mem::forget` is not marked unsafe
/// is a bug in the Rust standard library.
Copy link

@bb010g bb010g Oct 18, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wasn't std::mem::forget actually being safe, against pre-1.0 thoughts/desires, the whole issue with the Leakpocalypse?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, nevermind, this documentation was covered & changed by #30 & #31.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants