Message 232246 - 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	josh.r
Recipients	josh.r, serhiy.storchaka
Date	2014年12月06日.15:55:28
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1417881328.98.0.646919280576.issue23001@psf.upfronthosting.co.za>

Content
In the event of calls back into Python code in multithreaded execution (or GIL release), this would mean you no longer have guarantees as to the contents (or even the validity) of the pointer you get back. I'd think the only safe way to accept mutable buffers would be to use the s, z, y* codes, which lock the buffer to prevent resize/destruction. Do we want to open segfault vulnerabilities in arbitrary functions?

Content

In the event of calls back into Python code in multithreaded execution (or GIL release), this would mean you no longer have guarantees as to the contents (or even the validity) of the pointer you get back. I'd think the only safe way to accept mutable buffers would be to use the s*, z*, y* codes, which lock the buffer to prevent resize/destruction. Do we want to open segfault vulnerabilities in arbitrary functions?

History
Date	User	Action	Args
2014年12月06日 15:55:29	josh.r	set	recipients: + josh.r, serhiy.storchaka
2014年12月06日 15:55:28	josh.r	set	messageid: <1417881328.98.0.646919280576.issue23001@psf.upfronthosting.co.za>
2014年12月06日 15:55:28	josh.r	link	issue23001 messages
2014年12月06日 15:55:28	josh.r	create

homepage