per-slab canary values are good enough for now

pull/69/head
Daniel Micay 2018-11-05 18:05:56 -05:00
parent 3a488c9a27
commit 2d892e58ad
1 changed files with 0 additions and 2 deletions

View File

@ -211,8 +211,6 @@ was a bit less important and if a core goal was finding latent bugs.
and then later detect overflows/underflows and then later detect overflows/underflows
* High entropy per-slab random values * High entropy per-slab random values
* Leading byte is zeroed to contain C string overflows * Leading byte is zeroed to contain C string overflows
* [in-progress] Mangled into a unique value per slab slot (although not
with a strong keyed hash due to performance limitations)
* Possible slab locations are skipped and remain memory protected, leaving slab * Possible slab locations are skipped and remain memory protected, leaving slab
size class regions interspersed with guard pages size class regions interspersed with guard pages
* Zero size allocations are a dedicated size class with the entire region * Zero size allocations are a dedicated size class with the entire region