Message 325647 - 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	ronaldoussoren
Recipients	gregory.p.smith, pablogsal, ronaldoussoren, serhiy.storchaka, vstinner
Date	2018年09月18日.14:05:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1537279555.56.0.956365154283.issue34663@psf.upfronthosting.co.za>

Content
vfork() is more dangerous than fork() because the parent and child processes share memory (not copy-on-write, but really the same memory). Whether or not this affects posix_spawn depends on its implementation (to give a very vague statement). Glibc already uses vfork() in a number of cases, I'd expect that those are the cases where it is safe to use vfork() in the implementation of posix_spawn in the context of glibc. I'd therefore carefully test the use of vfork() in other cases to make sure those don't affect the parent process.

Content

vfork() is more dangerous than fork() because the parent and child processes share memory (not copy-on-write, but really the same memory). Whether or not this affects posix_spawn depends on its implementation (to give a very vague statement).
Glibc already uses vfork() in a number of cases, I'd expect that those are the cases where it is safe to use vfork() in the implementation of posix_spawn in the context of glibc. I'd therefore carefully test the use of vfork() in other cases to make sure those don't affect the parent process.

History
Date	User	Action	Args
2018年09月18日 14:05:55	ronaldoussoren	set	recipients: + ronaldoussoren, gregory.p.smith, vstinner, serhiy.storchaka, pablogsal
2018年09月18日 14:05:55	ronaldoussoren	set	messageid: <1537279555.56.0.956365154283.issue34663@psf.upfronthosting.co.za>
2018年09月18日 14:05:55	ronaldoussoren	link	issue34663 messages
2018年09月18日 14:05:55	ronaldoussoren	create

homepage