6562843997
weren't needed, and their existance interfered with things in subtle ways. One of these subtle ways was that malloc could be different based on what files were included when (even within the same .c file, it turns out). Move to a single malloc implementation as well by adding the calls to setheap() to gptboot.c and zfsboot.c. Once upon a time, these boot loaders strove to not use libstand. However, with the proliferation of features, that striving is too hard for too little gain and lead to stupid mistakes. This fixes the GELI-enabled (but not even using) boot environment. The geli routines were calling libstand malloc but zfsboot.c and gptboot.c were using the mini libstand malloc, so this failed when we tried to probe for GELI partitions. Subtle changes in build order when moving to self-contained stand build in r326593 toggled what it used from one type to another due to odd nesting of the zfs implementation code that differed subtly between zfsloader and zfsboot. Sponsored by: Netflix |
||
|---|---|---|
| .. | ||
| boot0 | ||
| boot0sio | ||
| boot2 | ||
| btx | ||
| cdboot | ||
| common | ||
| gptboot | ||
| gptzfsboot | ||
| kgzldr | ||
| libfirewire | ||
| libi386 | ||
| loader | ||
| mbr | ||
| pmbr | ||
| pxeldr | ||
| zfsboot | ||
| zfsloader | ||
| boot.ldscript | ||
| Makefile | ||
| Makefile.inc | ||