Mercurial > cpython-lru_cache-weakref
diff Python/pystate.c @ 69637:7b7ad9a88451 3.2
Issue #10517: After fork(), reinitialize the TLS used by the PyGILState_*
APIs, to avoid a crash with the pthread implementation in RHEL 5. Patch
by Charles-François Natali.
| author | Antoine Pitrou <solipsis@pitrou.net> |
|---|---|
| date | Wed, 27 Apr 2011 19:28:05 +0200 |
| parents | dc245d681901 |
| children | 2caf82aee7a4 c8f283cd3e6e |
line wrap: on
line diff
--- a/Python/pystate.c Wed Apr 27 18:13:42 2011 +0200 +++ b/Python/pystate.c Wed Apr 27 19:28:05 2011 +0200 @@ -585,6 +585,23 @@ autoInterpreterState = NULL; } +/* Reset the TLS key - called by PyOS_AfterFork. + * This should not be necessary, but some - buggy - pthread implementations + * don't flush TLS on fork, see issue #10517. + */ +void +_PyGILState_Reinit(void) +{ + PyThreadState *tstate = PyGILState_GetThisThreadState(); + PyThread_delete_key(autoTLSkey); + if ((autoTLSkey = PyThread_create_key()) == -1) + Py_FatalError("Could not allocate TLS entry"); + + /* re-associate the current thread state with the new key */ + if (PyThread_set_key_value(autoTLSkey, (void *)tstate) < 0) + Py_FatalError("Couldn't create autoTLSkey mapping"); +} + /* When a thread state is created for a thread by some mechanism other than PyGILState_Ensure, it's important that the GILState machinery knows about it so it doesn't try to create another thread state for the thread (this is