NEWS: Explain the s390 jmp_buf / ucontext_t ABI change reversal.

2 files changed, 16 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index d1f3986..e7b08e4 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  Roland McGrath  <roland@hack.frob.com>
 
 	* sysdeps/generic/safe-fatal.h: New file.
diff --git a/NEWS b/NEWS
index 36ed072..5a240de 100644
--- a/NEWS
+++ b/NEWS
@@ -24,6 +24,17 @@ Version 2.20
   17050, 17058, 17061, 17062, 17069, 17075, 17078, 17079, 17084, 17086,
   17088, 17092, 17097, 17125, 17135, 17137, 17150, 17153, 17213.
 
+* 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.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 wil 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.
+
 * Support for file description locks is added to systems running the
   Linux kernel. The standard file locking interfaces are extended to
   operate on file descriptions, not file descriptors, via the use of