Drop vfork support #279
Merged
Drop vfork support #279
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
`vfork` is something of a relic, originally introduced as a (rather unsafe) optimisation of `fork` in 3.0BSD, allowing the user to eliminate the cost of cloning the parent process's address space (as early BSDs would do) when `fork`ing with the intent of immediately `exec`ing. However, its design has long been considered a mistake (being nigh impossible to use safely in a multithreaded environment), its benefits have largely vanished (since modern operating systems rely on virtual memory to remap the parent's address space as copy-on-write instead of copying), and nearly all platforms now consider it to be an alias of `fork`. Remove `process`'s support for `vfork`. Fixes haskell#261.
snoyberg
approved these changes
Mar 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
vforkis something of a relic, originally introduced as a (rather unsafe) optimisation offorkin 3.0BSD, allowing the user to eliminate the cost of cloning the parent process's address space (as early BSDs would do) whenforking with the intent of immediatelyexecing.However, its design has long been considered a mistake (being nigh impossible to use safely in a multithreaded environment), its benefits have largely vanished (since modern operating systems rely on virtual memory to remap the parent's address space as copy-on-write instead of copying), and nearly all platforms now consider it to be an alias of
fork.Remove
process's support forvfork.Fixes #261.