document allocator state region

This commit is contained in:
Daniel Micay 2018-10-15 15:43:46 -04:00
parent 1c9e0d88a5
commit da8e9aa1d8

View File

@ -184,6 +184,8 @@ was a bit less important and if a core goal was finding latent bugs.
* State within global variables is entirely read-only after initialization
with pointers to the isolated allocator state so leaking the address of
the library doesn't leak the address of writable state
* [in-progress] Allocator state is located within a dedicated region with
high entropy randomly sized guard regions around it
* [in-progress] Protection via Memory Protection Keys (MPK) on x86\_64
* [implementing stronger state protection is in-progress]
* Extension for retrieving the size of allocations with fallback