diff options
| -rw-r--r-- | ChangeLog | 5 | ||||
| -rw-r--r-- | NEWS | 11 |
2 files changed, 16 insertions, 0 deletions
diff --git a/ChangeLog b/ChangeLog index c8978795e3..e274c7febb 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2014-08-01 Stefan Liebler <stli@linux.vnet.ibm.com> + + * NEWS: Explain the s390 jmp_buf / ucontext_t ABI change + reversal. + 2014-07-31 Stefan Liebler <stli@linux.vnet.ibm.com> * sysdeps/s390/Makefile: Delete file. diff --git a/NEWS b/NEWS index 71b6ad5c88..352b8a599b 100644 --- a/NEWS +++ b/NEWS @@ -12,6 +12,17 @@ Version 2.19.1 15946, 16545, 16574, 16623, 16695, 16878, 16882, 16885, 16916, 16932, 16943, 16958, 17048, 17069, 17137. +* Reverted change of ABI data structures for s390 and s390x: + On s390 and s390x the size of struct ucontext and jmp_buf was increased in + 2.19. This change is reverted in 2.19.1 and 2.20. The introduced 2.19 symbol + versions of getcontext, setjmp, _setjmp, __sigsetjmp, longjmp, _longjmp, + siglongjmp are preserved pointing straight to the same implementation as the + old ones. Given that, new callers will simply provide a too-big buffer to + these functions. Any applications/libraries out there that embed jmp_buf or + ucontext_t in an ABI-relevant data structure that have already been rebuilt + against 2.19 headers will have to rebuilt again. This is necessary in any + case to revert the breakage in their ABI caused by the glibc change. + * CVE-2014-4043 The posix_spawn_file_actions_addopen implementation did not copy the path argument. This allowed programs to cause posix_spawn to deference a dangling pointer, or use an unexpected pathname argument if |