From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 50817 invoked by alias); 31 Jan 2020 10:04:09 -0000 Mailing-List: contact glibc-cvs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: glibc-cvs-owner@sourceware.org List-Subscribe: Received: (qmail 50761 invoked by uid 10103); 31 Jan 2020 10:04:08 -0000 Date: Fri, 31 Jan 2020 10:04:00 -0000 Message-ID: <20200131100408.50760.qmail@sourceware.org> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Szabolcs Nagy To: glibc-cvs@sourceware.org Subject: [glibc] Add NEWS entry about 64-bit time_t syscall use on 32-bit targets X-Act-Checkin: glibc X-Git-Author: Szabolcs Nagy X-Git-Refname: refs/heads/master X-Git-Oldrev: 9baa46aa7b1aa56c8fb313013bb9aecf4ed96504 X-Git-Newrev: 2cd01a1df2afc16ada1ce8479fbf888a803270ea X-SW-Source: 2020-q1/txt/msg00207.txt https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=2cd01a1df2afc16ada1ce8479fbf888a803270ea commit 2cd01a1df2afc16ada1ce8479fbf888a803270ea Author: Szabolcs Nagy Date: Thu Jan 30 10:40:01 2020 +0000 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 Diff: --- NEWS | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/NEWS b/NEWS index 10814ef..64282d4 100644 --- a/NEWS +++ b/NEWS @@ -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