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.

Author pitrou
Recipients florin.papa, pitrou, r.david.murray, rhettinger, skrah, vstinner, zach.ware
Date 2015-11-24.12:41:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448368885.28.0.344750258363.issue25300@psf.upfronthosting.co.za>
In-reply-to
Content
Hi,

I've reviewed the latest patch.
I have a more general question: the patch sprinkles some Py_INIT_BOUNDS() calls in various places. What the macro does is set the pointer's bounds to "INIT", which basically means disable any checks (the pointer is allowed to access all memory). Is there a reason for that? MPX checks for out-of-bounds accesses, so setting pointer bounds to "INIT" seems to defeat the point.

(if MPX otherwise complains about out-of-bounds accesses in CPython, perhaps they are genuine bugs that deserve fixing, or perhaps the annotations in the patch are not good enough)
History
Date User Action Args
2015-11-24 12:41:25pitrousetrecipients: + pitrou, rhettinger, vstinner, r.david.murray, skrah, zach.ware, florin.papa
2015-11-24 12:41:25pitrousetmessageid: <1448368885.28.0.344750258363.issue25300@psf.upfronthosting.co.za>
2015-11-24 12:41:25pitroulinkissue25300 messages
2015-11-24 12:41:25pitroucreate