use _ALIGN() which is uhm a bit OpenBSD-specific, but it means we
don't need to use sys/param.h at all, guess which one i believe is
greater namespace polution
ok otto

Use _MAX_PAGE_SHIFT, rather than #ifdef mips64
ok guenther kettenis

use consistent style for for loop in unmap(), no functional change

keep in sync with ld.so malloc.c

- An error in the multithreaded case could print the wrong function name
- Start with a full page of struct region_info's
- Save an mprotect in the init code: allocate 3 pages with none and
make th

- An error in the multithreaded case could print the wrong function name
- Start with a full page of struct region_info's
- Save an mprotect in the init code: allocate 3 pages with none and
make the middle page r/w instead of a r/w allocation and two calls to make the
guard pages none

show more ...

- do not junk pages returned by free_bytes(), all freed chunks are already
junked
- freezero(): only clear requested size

Zap the rotor, it was a wrong idea. Cluebat applied by kshe who
came also up with this diff. Simple, no bias and benchmarks show the extra
random calls disappear in te measurement noise.

Move to ffs(3) for bitmask scanning. I played with this earlier,
but at that time ffs function calls were generated instead of the
compiler inlining the code. Now that ffs is marked protected in
lib

Move to ffs(3) for bitmask scanning. I played with this earlier,
but at that time ffs function calls were generated instead of the
compiler inlining the code. Now that ffs is marked protected in
libc this is handled better. Thanks to kshe who prompted me to
look at this again.

show more ...

optimization and some cleanup; mostly from kshe (except the unmap() part)

Only init chunk_info once, plus some moving of code to group related functions.

step one in avoiding unneccesary init of chunk_info;
some cleanup; tested by sthen@ on a ports build

's' should include 'f'; from Jacqueline Jolicoeur

Restore a return that was inadvertently removed from freezero() in r1.234,
which results in an internal double free when internal functions are not
in use.

ok otto@

do not return f() where f is a void function; loop var type fix

Use dprintf instead of snprintf/write

Make delayed free non-optional and make F do an extensive double free check.
ok tb@ tedu@

mapalign returns MAP_FAILED for failuer; from George Koehler

check double free before canary for chunks; ok millert@

two MALLOC_STATS only tweaks; one from David CARLIER, the other found by clang

one more instance of the previous commit; also initialize ->offset to a
definite value in the size == 0 case

Only access offset if canaries are enabled *and* size > 0, otherwise offset
is not initialized. Problem spotted by Carlin Bingham; ok phessler@ tedu@

port the RBT code to userland by making it part of libc.

src/lib/libc/gen/tree.c is a copy of src/sys/kern/subr_tree.c, but with
annotations for symbol visibility. changes to one should be reflected

port the RBT code to userland by making it part of libc.

src/lib/libc/gen/tree.c is a copy of src/sys/kern/subr_tree.c, but with
annotations for symbol visibility. changes to one should be reflected
in the other.

the malloc debug code that uses RB code is ported to RBT.

because libc provides the RBT code, procmap doesn't have to reach into
the kernel and build subr_tree.c itself now.

mild enthusiasm from many
ok guenther@

show more ...

- fix bug wrt posix_memalign(3) of blocks between half a page and a page
- document posix_memalign() does not play nice with reacallocarray(3) and
freezero(3)

For small allocations (chunk) freezero only validates the given
size if canaries are enabled. In that case we have the exact requested
size of the allocation. But we can at least check the given siz

For small allocations (chunk) freezero only validates the given
size if canaries are enabled. In that case we have the exact requested
size of the allocation. But we can at least check the given size
against the chunk size if C is not enabled. Plus add some braces
so my brain doesn't have to scan for dangling else problems when I
see this code.

show more ...

don't forget to fill in canary bytes for posix_memalign(3); reported by
and ok jeremy@