[PATCH] malloc/malloc.c: Mitigate null-byte overflow attacks

[DJ Delorie]

Moritz Eckert <m.eckert@cs.ucsb.edu> writes:
> I only placed the check before backward unlinks,

Ah, ok.

>> I wonder if we should add a "size_is_sane()" macro to check for
>> unreasonable sizes before we use them to compute pointers.
> That sounds like a good idea to me. Would you prefer a separate macro
> for prev_size and size that only gets the current chunk as a parameter or
> a single macro that gets a parameter what to check for?

I don't know, I was just wondering if there were some other way to
determine that a size has been corrupted other than consistency checks.