diff options
| author | jhb <jhb@FreeBSD.org> | 2015-04-09 19:36:06 +0000 |
|---|---|---|
| committer | jhb <jhb@FreeBSD.org> | 2015-04-09 19:36:06 +0000 |
| commit | 107a51b87f516e0a578d0a40ce21399c4d612e9d (patch) | |
| tree | 8c06a1ac00f83852efeab556cd073920fd1a6687 /lib | |
| parent | de91cfb1641ad37c56d8cc6360dd818198dd58e6 (diff) | |
| download | FreeBSD-src-107a51b87f516e0a578d0a40ce21399c4d612e9d.zip FreeBSD-src-107a51b87f516e0a578d0a40ce21399c4d612e9d.tar.gz | |
MFC 279949:
The System V ABI for amd64 allows functions to use space in a 128 byte
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.
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/libstand/Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/libstand/Makefile b/lib/libstand/Makefile index 359fa4a..7c253c8 100644 --- a/lib/libstand/Makefile +++ b/lib/libstand/Makefile @@ -27,7 +27,7 @@ CFLAGS+= -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float CFLAGS.gcc+= -mpreferred-stack-boundary=2 .endif .if ${MACHINE_CPUARCH} == "amd64" -CFLAGS+= -fPIC +CFLAGS+= -fPIC -mno-red-zone .endif .if ${MACHINE} == "pc98" CFLAGS+= -Os |
