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

diff --git a/ChangeLog b/ChangeLog
index d1f39867c43312c38b2c008b585f4c1c3c5c25ff..e7b08e4d6cfde4235cf539cdb7d796aa17851a88 100644 (file)
--- 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 36ed072b425002df3e33ca794d5ec6c2967b316f..5a240de0e4fdf1aeb1fc0a8918b162a0b8ffd581 100644 (file)
--- 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