emo/hardened_malloc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

document progress on protected allocator state

Browse Source
This commit is contained in:
Daniel Micay 2018-10-14 22:12:03 -04:00
parent da6fd5b5ef
commit 3504465584
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -155,10 +155,14 @@ allocation and then unmapped on free.
* 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 memory protected * Zero size allocations are memory protected
* Protected allocator metadata * Protected allocator state (including all metadata)
* Address space for metadata is entirely reserved during initialization and * Address space for state is entirely reserved during initialization and
never reused for allocations or anything else never reused for allocations or anything else
* [implementing stronger protection is in-progress] * 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] 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 * Extension for retrieving the size of allocations with fallback
to a sentinel for pointers not managed by the allocator to a sentinel for pointers not managed by the allocator
* Can also return accurate values for pointers *within* small allocations * Can also return accurate values for pointers *within* small allocations