@musllibc @RichFelker Then there's a choice between OpenBSD-style memory protection and/or glibc-style XOR for atexit, pthread_atfork, etc.
@CopperheadSec Headers/footers, if validated well, also go a long way towards mitigating exploitable off-by-1 heap overflows.
-
-
@RichFelker They are, but it can be better without the metadata there at all. Spending two extra bits per allocation isn't very significant. -
@CopperheadSec I've considered size-segregated pools with atomic TAS bitmaps to solve frag, overhead, and lock contention.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.