1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

bpo-39776: Lock ++interp->tstate_next_unique_id. (GH-18746) (#18746)

Browse Source 
- Threads created by PyGILState_Ensure() could have a duplicate tstate->id.
This commit is contained in:
Stefan Krah 2020-03-02 21:22:36 +01:00 committed by GitHub
parent 2d2f85517f
commit b3b9ade4a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Misc/NEWS.d/next/Core and Builtins/2020-03-02-20-12-33.bpo-39776.fNaxi_.rst Normal file
View File

@ -0,0 +1,6 @@
Fix race condition where threads created by PyGILState_Ensure() could get a
duplicate id.
This affects consumers of tstate->id like the contextvar caching machinery,
which could return invalid cached objects under heavy thread load (observed
in embedded scenarios).

3
Python/pystate.c
View File

@ -606,13 +606,12 @@ new_threadstate(PyInterpreterState *interp, int init)
tstate->context = NULL; tstate->context = NULL;
tstate->context_ver = 1; tstate->context_ver = 1;
tstate->id = ++interp->tstate_next_unique_id;
if (init) { if (init) {
_PyThreadState_Init(tstate); _PyThreadState_Init(tstate);
} }
HEAD_LOCK(runtime); HEAD_LOCK(runtime);
tstate->id = ++interp->tstate_next_unique_id;
tstate->prev = NULL; tstate->prev = NULL;
tstate->next = interp->tstate_head; tstate->next = interp->tstate_head;
if (tstate->next) if (tstate->next)