Skip to content

[3.10] bpo-47151: Fallback to fork when vfork fails in subprocess. (GH-32186) #32219

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.

Sign up for GitHub

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

Jump to bottom
Merged
miss-islington merged 1 commit into from
Mar 31, 2022
Merged

[3.10] bpo-47151: Fallback to fork when vfork fails in subprocess. (GH-32186) #32219

miss-islington merged 1 commit into from
Mar 31, 2022

Conversation

@miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Mar 31, 2022 •
edited
Loading

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 greg@krypto.org

Automerge-Triggered-By: GH:gpshead

@gpshead @miss-islington
bpo-47151: Fallback to fork when vfork fails in subprocess. (pythonGH…
cbc9705 
…-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 <greg@krypto.org>
@miss-islington miss-islington requested a review from gpshead as a code owner March 31, 2022 20:42
@bedevere-bot bedevere-bot mentioned this pull request Mar 31, 2022
Merged
@bedevere-bot bedevere-bot added the type-bug An unexpected behavior, bug, or error label Mar 31, 2022
@miss-islington
Copy link
Contributor Author

miss-islington commented Mar 31, 2022

@gpshead: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

miss-islington commented Mar 31, 2022

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

@miss-islington
Copy link
Contributor Author

miss-islington commented Mar 31, 2022

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

@miss-islington
Copy link
Contributor Author

miss-islington commented Mar 31, 2022

@gpshead: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 9ed179b into python:3.10 Mar 31, 2022
@miss-islington miss-islington deleted the backport-4a08c4c-3.10 branch March 31, 2022 21:09
@socketpair socketpair mannequin mentioned this pull request May 1, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gpshead gpshead gpshead approved these changes

Assignees

No one assigned

Labels

type-bug An unexpected behavior, bug, or error

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@miss-islington @gpshead @the-knights-who-say-ni @bedevere-bot