-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-47151: Fallback to fork when vfork fails in subprocess. #32186
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
Conversation
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.
lgtm :) Nice solution
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.
LGTM.
Thanks @gpshead for the PR 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
Sorry, @gpshead, I could not cleanly backport this to |
GH-32219 is a backport of this pull request to the 3.10 branch. |
…-32186) bpo-47151: Fallback to fork when vfork fails in subprocess. An OS kernel can specifically decide to disallow vfork() in a process. No need for that to prevent us from launching subprocesses. (cherry picked from commit 4a08c4c) Co-authored-by: Gregory P. Smith <[email protected]>
bpo-47151: Fallback to fork when vfork fails in subprocess. An OS kernel can specifically decide to disallow vfork() in a process. No need for that to prevent us from launching subprocesses. (cherry picked from commit 4a08c4c) Co-authored-by: Gregory P. Smith <[email protected]>
vfork()
can return -1 and seterrno
. We now fall back tofork()
in that situation as one possible error isEINVAL
indicating that the kernel doesn't permit vfork from the current process. See the bug.https://bugs.python.org/issue47151