Extend kern_malloc.c internals to also cover contigmalloc(9) by a
"slab cookie" and not just malloc/malloc_large. This allows us to
call free(9) even on contigmalloc(9) addresses.
Extend the contigmalloc(9) man page with a small additional note that
free(9) also works now.
The implementation also adds additional chacks now under INVARIANTS;
e.g. validity of a cookie (allocation type) in various places as well
as size and allocation type checks for contigfree(9).
The way this is done (free working for contigmalloc) will hide the
UMA/VM bits from a consumer which may otherwise need to know whether
the original allocation was by malloc or contigmalloc by looking at
the cookie (likely via an accessor function). This simplifies
the implementation of consumers of mixed environments a lot.
This is preliminary work to allow LinuxKPI to be adjusted to better
play by the rules Linux puts out for various allocations.
Most of this was described/explained to me by jhb.
One may observe that realloc(9) is currently unchanged (and contrary
to [contig]malloc/[contig]free an implementation may need access
the "slab cookie" information given it will likely be implementation
dependent which allocation to use if size changes beyond the usable
size of the initial allocation).
Described by: jhb
Sponsored by: The FreeBSD Foundation
MFC after: 3 days