ad06e987b1
redzone below the stack pointer for scratch space and requires interrupt and signal frames to avoid overwriting it. However, EFI uses the Windows ABI which does not support this. As a result, interrupt handlers in EFI push their interrupt frames directly on top of the stack pointer. If the compiler used the red zone in a function in the EFI loader, then a device interrupt that occurred while that function was running could trash its local variables. In practice this happens fairly reliable when using gzipfs as an interrupt during decompression can trash the local variables in the inflate_table() function resulting in corrupted output or hangs. Fix this by disabling the redzone for amd64 EFI binaries. This requires building not only the loader but any libraries used by the loader without redzone support. Thanks to Jilles for pointing me at the redzone once I found the stack corruption. Differential Revision: https://reviews.freebsd.org/D2054 Reviewed by: imp MFC after: 2 weeks Sponsored by: Cisco Systems, Inc. |
||
|---|---|---|
| .. | ||
| amd64 | ||
| arm | ||
| i386 | ||
| mips | ||
| mips64 | ||
| powerpc | ||
| softwords | ||
| sparc64 | ||
| dict.c | ||
| ficl.c | ||
| ficl.h | ||
| fileaccess.c | ||
| float.c | ||
| loader.c | ||
| Makefile | ||
| math64.c | ||
| math64.h | ||
| prefix.c | ||
| search.c | ||
| stack.c | ||
| testmain.c | ||
| tools.c | ||
| unix.c | ||
| vm.c | ||
| words.c | ||