-
Notifications
You must be signed in to change notification settings - Fork 13.4k
std: fix aliasing bug in UNIX process implementation #138896
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
base: master
Are you sure you want to change the base?
Conversation
r? @Noratrieb rustbot has assigned @Noratrieb. Use |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
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.
looks like we got boxed again 💀. but the fixed implementation is nicer anyways, so that's cool.
but can you add a SAFETY comment to the new unsafe blocks? it does all looks fine to me.
`CStringArray` contained both `CString`s and their pointers. Unfortunately, since `CString` uses `Box`, moving the `CString`s into the `Vec` can (under stacked borrows) invalidate the pointer to the string, meaning the resulting `Vec<*const c_char>` was, from an opsem perspective, unusable. This PR removes removes the `Vec<CString>` from `CStringArray`, instead recreating the `CString`/`CStr` from the pointers when necessary. Also,`CStringArray` is now used for the process args as well, the old implementation was suffering from the same kind of bug.
☔ The latest upstream changes (presumably #141331) made this pull request unmergeable. Please resolve the merge conflicts. |
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.
r=me after fixing conflicts
CStringArray
contained bothCString
s and their pointers. Unfortunately, sinceCString
usesBox
, moving theCString
s into theVec
can (under stacked borrows) invalidate the pointer to the string, meaning the resultingVec<*const c_char>
was, from an opsem perspective, unusable. This PR removes removes theVec<CString>
fromCStringArray
, instead recreating theCString
/CStr
from the pointers when necessary. Also,CStringArray
is now used for the process args as well, the old implementation was suffering from the same kind of bug.