The PTRDIFF_MAX object size limit needed to be extended to mremap too: https://android-review.googlesource.com/#/c/181202/ http://www.openwall.com/lists/musl/2015/10/31/1 ….
@thegrugq @CopperheadSec There's not even a clear party to blame for the "bug". Overflows in reasonable pointer arith. = hopelessly bad QoI.
-
-
@RichFelker@thegrugq The standard should really just forbid objects larger than PTRDIFF_MAX but they're too afraid of breaking anything. -
@RichFelker@thegrugq Could be done on the kernel's side of the syscalls but that's never going to happen on Linux (maybe in@grsecurity). -
@RichFelker@thegrugq@grsecurity The merging of memory spans in jemalloc is a case where the kernel doing it wouldn't be enough though. -
@CopperheadSec@thegrugq@grsecurity Kernel could ensure it never maps >PTRDIFF_MAX worth of contiguous virtual memory.
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.