refactor: redefine ForkptyResult to avoid uninited master field #2315
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.
What does this PR do
Before this PR, our
ForkptrResult
was defined like this:The problem with this definition is that the
master
field won't be initialized (actually, it won't be accessed at all) within the forked child process, which means that ourforkpty()
was callingOwnedFd::from_raw_fd(an uninitialized memory)
, if the dirty value stored in that uninitialized memory is not a valid value for a file descriptor (say -1), then this function will panic, making the child process panic.This PR redefines the
ForkptyResult
type so that themaster
field is only present in the parent process.cc @Xeom
related to #2312
Checklist:
CONTRIBUTING.md