Message 256815 - Python tracker

➜

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.

In-reply-to
Author	emptysquare
Recipients	emptysquare
Date	2015年12月21日.23:19:32
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1450739972.22.0.163393011494.issue25920@psf.upfronthosting.co.za>

Content
On some platforms there's an exclusive lock in socketmodule, used for getaddrinfo, gethostbyname, gethostbyaddr. A thread can hold this lock while another forks, leaving it locked forever in the child process. Calls to these functions in the child process will hang. (I wrote some more details here: https://emptysqua.re/blog/getaddrinfo-deadlock/ ) I propose that this is a bug, and that it can be fixed in PyOS_AfterFork, where a few similar locks are already reset.

Content

On some platforms there's an exclusive lock in socketmodule, used for getaddrinfo, gethostbyname, gethostbyaddr. A thread can hold this lock while another forks, leaving it locked forever in the child process. Calls to these functions in the child process will hang.
(I wrote some more details here: https://emptysqua.re/blog/getaddrinfo-deadlock/ )
I propose that this is a bug, and that it can be fixed in PyOS_AfterFork, where a few similar locks are already reset.

History
Date	User	Action	Args
2015年12月21日 23:19:32	emptysquare	set	recipients: + emptysquare
2015年12月21日 23:19:32	emptysquare	set	messageid: <1450739972.22.0.163393011494.issue25920@psf.upfronthosting.co.za>
2015年12月21日 23:19:32	emptysquare	link	issue25920 messages
2015年12月21日 23:19:32	emptysquare	create

homepage