Author yselivanov
Recipients emptysquare, ionelmc, vstinner, yselivanov
Date 2015-12-21.23:55:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1450742127.47.0.933597540005.issue25920@psf.upfronthosting.co.za>
In-reply-to
Content
Maybe instead of releasing the lock in the forked child process, we should try to acquire the lock in the os.fork() implementation, and then release it?

Otherwise, suppose that a call to getaddrinfo (call #1) takes a long amount of time.  In the middle of it we fork, and then immediately try to call getaddrinfo (call #2, and call #1 is still happening) for some other address. At this point, since getaddrinfo isn't threadsafe, something bad will happen.
History
Date User Action Args
2015-12-21 23:55:27yselivanovsetrecipients: + yselivanov, vstinner, ionelmc, emptysquare
2015-12-21 23:55:27yselivanovsetmessageid: <1450742127.47.0.933597540005.issue25920@psf.upfronthosting.co.za>
2015-12-21 23:55:27yselivanovlinkissue25920 messages
2015-12-21 23:55:27yselivanovcreate