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 | izbyshev |
|---|---|
| Recipients | benjamin.peterson, gregory.p.smith, izbyshev, pitrou, siddhesh, skrah, steve.dower, vstinner |
| Date | 2018年10月23日.16:34:29 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1540312470.0.0.788709270274.issue33015@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Such casts will also trigger a CFI violation if somebody tries to build Python (and the libc, in this case) with a signature-based CFI [1, 2]. It checks that the compile-time callee signature matches the signature of the actually called function in runtime. [1] https://clang.llvm.org/docs/ControlFlowIntegrity.html [2] https://android-developers.googleblog.com/2018/10/control-flow-integrity-in-android-kernel.html |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018年10月23日 16:34:30 | izbyshev | set | recipients: + izbyshev, gregory.p.smith, pitrou, vstinner, benjamin.peterson, skrah, steve.dower, siddhesh |
| 2018年10月23日 16:34:30 | izbyshev | set | messageid: <1540312470.0.0.788709270274.issue33015@psf.upfronthosting.co.za> |
| 2018年10月23日 16:34:29 | izbyshev | link | issue33015 messages |
| 2018年10月23日 16:34:29 | izbyshev | create | |