mirror of https://github.com/python/cpython
bpo-39776: Lock ++interp->tstate_next_unique_id. (GH-18746) (#18746)
- Threads created by PyGILState_Ensure() could have a duplicate tstate->id.
This commit is contained in:
parent
2d2f85517f
commit
b3b9ade4a3
|
@ -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).
|
|
@ -606,13 +606,12 @@ new_threadstate(PyInterpreterState *interp, int init)
|
|||
tstate->context = NULL;
|
||||
tstate->context_ver = 1;
|
||||
|
||||
tstate->id = ++interp->tstate_next_unique_id;
|
||||
|
||||
if (init) {
|
||||
_PyThreadState_Init(tstate);
|
||||
}
|
||||
|
||||
HEAD_LOCK(runtime);
|
||||
tstate->id = ++interp->tstate_next_unique_id;
|
||||
tstate->prev = NULL;
|
||||
tstate->next = interp->tstate_head;
|
||||
if (tstate->next)
|
||||
|
|
Loading…
Reference in New Issue