aggressive write-after-free check is implemented

This commit is contained in:
Daniel Micay 2018-09-11 05:17:22 -04:00
parent 61684925e8
commit b52d9ca831

View File

@ -76,8 +76,7 @@ allocation and then unmapped on free.
* [in-progress] Randomized allocation of slabs * [in-progress] Randomized allocation of slabs
* [more randomization coming as the implementation is matured] * [more randomization coming as the implementation is matured]
* Slab allocations are zeroed on free and large allocations are unmapped * Slab allocations are zeroed on free and large allocations are unmapped
* [in-progress] Detection of write-after-free by verifying zero filling is * Detection of write-after-free by verifying zero filling is intact
intact
* Memory in fresh allocations is consistently zeroed due to it either being * Memory in fresh allocations is consistently zeroed due to it either being
fresh pages or zeroed on free after previous usage fresh pages or zeroed on free after previous usage
* [in-progress] Delayed free via a combination of FIFO and randomization for * [in-progress] Delayed free via a combination of FIFO and randomization for