diff options
author | Ulrich Weigand <Ulrich.Weigand@de.ibm.com> | 2013-12-04 06:41:52 -0600 |
---|---|---|
committer | Adhemerval Zanella <azanella@linux.vnet.ibm.com> | 2013-12-04 07:41:37 -0600 |
commit | 5162e7dd96efcd9b45c1dc1471a964d45278b1e1 (patch) | |
tree | 82cf3f29b872248b8ca7d82e5706c70aaaf64da3 /sysdeps/powerpc | |
parent | 19e3372ba4538f85b6c73361feaf408ae0e65ebe (diff) | |
download | glibc-5162e7dd96efcd9b45c1dc1471a964d45278b1e1.tar.gz glibc-5162e7dd96efcd9b45c1dc1471a964d45278b1e1.tar.xz glibc-5162e7dd96efcd9b45c1dc1471a964d45278b1e1.zip |
PowerPC64: Fix incorrect CFI in *context routines
The context established by "makecontext" has a link register pointing back to an error path within the makecontext routine. This is currently covered by the CFI FDE for makecontext itself, which is simply wrong for the stack frame *inside* the context. When trying to unwind (e.g. doing a backtrace) in a routine inside a context created by makecontext, this can lead to uninitialized stack slots being accessed, causing the unwinder to crash in the worst case. Similarly, during parts of the "setcontext" routine, when the stack pointer has already been switched to point to the new context, the address range is still covered by the CFI FDE for setcontext. When trying to unwind in that situation (e.g. backtrace from an async signal handler for profiling), it is again possible that the unwinder crashes. Theses are all problems in existing code, but the changes in stack frame layout appear to make the "worst case" much more likely in the ELFv2 ABI context. This causes regressions e.g. in the libgo testsuite on ELFv2. This patch fixes this by ending the makecontext/setcontext FDEs before those problematic parts of the assembler, similar to what is already done on other platforms. This fixes the libgo regression on ELFv2.
Diffstat (limited to 'sysdeps/powerpc')
0 files changed, 0 insertions, 0 deletions