]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.12] gh-77377: Ensure multiprocessing SemLock is valid for spawn-based Process...
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Wed, 23 Aug 2023 23:44:07 +0000 (16:44 -0700)
committerGitHub <noreply@github.com>
Wed, 23 Aug 2023 23:44:07 +0000 (01:44 +0200)
commit9cf49aaaa0a08d430cd54a1c9ea022d40463bbfe
treef5b7a83b765a2ca316a14e545f782fe23c6ce820
parent3aa7df6544950c21be57bd4bee5edbef4d196fce
[3.12] gh-77377: Ensure multiprocessing SemLock is valid for spawn-based Process before serializing it (GH-107275) (#108377)

gh-77377: Ensure multiprocessing SemLock is valid for spawn-based Process before serializing it (GH-107275)

Ensure multiprocessing SemLock is valid for spawn Process before serializing it.

Creating a multiprocessing SemLock with a fork context, and then trying to pass it to a spawn-created Process, would segfault if not detected early.

---------

(cherry picked from commit 1700d34d314f5304a7a75363bda295a8c15c371f)

Co-authored-by: albanD <desmaison.alban@gmail.com>
Co-authored-by: blurb-it[bot] <43283697+blurb-it[bot]@users.noreply.github.com>
Co-authored-by: Antoine Pitrou <pitrou@free.fr>
Lib/multiprocessing/synchronize.py
Lib/test/_test_multiprocessing.py
Misc/NEWS.d/next/Core and Builtins/2023-07-25-22-35-35.gh-issue-77377.EHAbXx.rst [new file with mode: 0644]