Issue 23565: local_clear walks the list of threads without holding head_lock.

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

This issue has been migrated to GitHub: https://github.com/python/cpython/issues/67753

classification

Title:	local_clear walks the list of threads without holding head_lock.
Type:	behavior	Stage:
Components:	Library (Lib)	Versions:

process

Status:	open	Resolution:
Dependencies:		Superseder:
Assigned To:		Nosy List:	pitrou, stutzbach, vstinner
Priority:	normal	Keywords:

Created on 2015-03-02 19:45 by stutzbach, last changed 2022-04-11 14:58 by admin.

Messages (1)
msg237078 - (view)	Author: Daniel Stutzbach (stutzbach)	Date: 2015-03-02 19:45
local_clear in _threadmodule.c walks the list of threads without holding head_mutex. Since the list of threads can change when holding only head_mutex and not on the GIL, the list can change while local_clear is executing, which may cause Bad Things to happen.

msg237078 - (view)

Author: Daniel Stutzbach (stutzbach) (Python committer)

Date: 2015-03-02 19:45

local_clear in _threadmodule.c walks the list of threads without holding head_mutex.  Since the list of threads can change when holding only head_mutex and not on the GIL, the list can change while local_clear is executing, which may cause Bad Things to happen.

History
Date	User	Action	Args
2022-04-11 14:58:13	admin	set	github: 67753
2021-06-18 23:26:27	iritkatriel	set	nosy: + pitrou, vstinner
2015-03-02 19:45:23	stutzbach	create