Add NEWS entry about 64-bit time_t syscall use on 32-bit targets

This internal change ideally should not affect the public API or ABI,
but there is a widespread use of seccomp sandboxes, even on 32-bit
targets, that don't handle new Linux syscall usage well, so it's
worth mentioning in the NEWS.

Co-authored-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
This commit is contained in:
Szabolcs Nagy 2020-01-30 10:40:01 +00:00
parent 9baa46aa7b
commit 2cd01a1df2

7
NEWS
View File

@ -124,6 +124,13 @@ Deprecated and removed features, and other changes affecting compatibility:
The GNU C Library can be built with --enable-kernel=4.8.0 in order to keep a
non-executable stack while dropping support for older kernels.
* System call wrappers for time system calls now use the new time64 system
calls when available. On 32-bit targets, these wrappers attempt to call
the new system calls first and fall back to the older 32-bit time system
calls if they are not present. This may cause issues in environments
that cannot handle unsupported system calls gracefully by returning
-ENOSYS. Seccomp sandboxes are affected by this issue.
Changes to build and runtime requirements:
* It is no longer necessary to have recent Linux kernel headers to build