Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2399698ybc; Wed, 13 Nov 2019 13:58:17 -0800 (PST) X-Google-Smtp-Source: APXvYqz573Oyz3Ze6SXJhSQ7hv95ZG2+UKxbaf3HGiJGRis65DEXkP5HNGzB1/OEaG7FozRh/q39 X-Received: by 2002:aa7:d346:: with SMTP id m6mr6311799edr.234.1573682297304; Wed, 13 Nov 2019 13:58:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573682297; cv=none; d=google.com; s=arc-20160816; b=yXGzjNFBdMuXvy1nica7NgEBciDdw2b9q64QWMfiXPiCx5uYh8RKIB9W1HD4GEZ8Sq LwgIsjyB10rqM7vnudRYXVOdVddzQNkePVrrMOWvMFV2aXJwINp/h/ybkwnNlhv/nabP 2W0cSW4UX2JwBG0ABQMdwbH9G04I8FWBXwbL6IxDMXmrLcJjY5XGWRpl7ZyUncQEm625 sxD5d+JarDRJCM9jmU2CIb4N/QNIg3ZqnpaE/PN7zaK3r7l4fP8tCT54oT+RYNVJHAyT gN+TZ91w/L2TGpgqz92NtEt3ecDWXNCAZ9dM+nOYqp65NqmNEL0XYcA3rYowiN7rIP65 mnpA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=ymyJHTWgpj54/dsDwdkGKYa46GVC6/XVQbeCZ4iXJUc=; b=aNJxHZq/wqFud6mLRDcMZ6UpO19+XTL8qQZqApNMdxhrXOYZjbtKYczvqLYpqPbwCn tKo4NH2IdrIibYptAaI20FtIK5EltqrNoh0Op8BbGLs/oxEctfa3ulLc+viocIV5VIaj lU3rBKzIghCi684BhiFiUJeGN414cvLEx3DJX/K53fvIvFdzCToWTCUQfC2sLlSRH1cs ybzsQwW+otZbprD4+jKv2mpa3kBcVUm8CEYQ4+hHkt2n/p3N11/2tsj+VCFy3/Swqfw8 B+PSc2ehCl7DJuxXZOLT18Ed10aErPC2ki3NbX7b0y4K8HqPP4ldx+AsA/ft7gpyb6Te Gmkw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n19si1931428ejk.264.2019.11.13.13.57.52; Wed, 13 Nov 2019 13:58:17 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726505AbfKMV45 (ORCPT + 99 others); Wed, 13 Nov 2019 16:56:57 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:39226 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726162AbfKMV44 (ORCPT ); Wed, 13 Nov 2019 16:56:56 -0500 Received: from p5b06da22.dip0.t-ipconnect.de ([91.6.218.34] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iV0ch-00077n-F2; Wed, 13 Nov 2019 22:56:23 +0100 Date: Wed, 13 Nov 2019 22:56:22 +0100 (CET) From: Thomas Gleixner To: Arnd Bergmann cc: y2038@lists.linaro.org, Greentime Hu , Vincent Chen , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , "David S. Miller" , Andy Lutomirski , Ingo Molnar , Borislav Petkov , x86@kernel.org, Jeff Dike , Richard Weinberger , Anton Ivanov , linux-kernel@vger.kernel.org, "H. Peter Anvin" , Vincenzo Frascino , Christophe Leroy , "Eric W. Biederman" , linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org, linux-um@lists.infradead.org Subject: Re: [PATCH 03/23] y2038: vdso: change timeval to __kernel_old_timeval In-Reply-To: <20191108210824.1534248-3-arnd@arndb.de> Message-ID: References: <20191108210236.1296047-1-arnd@arndb.de> <20191108210824.1534248-3-arnd@arndb.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 8 Nov 2019, Arnd Bergmann wrote: > The gettimeofday() function in vdso uses the traditional 'timeval' > structure layout, which will be incompatible with future versions of > glibc on 32-bit architectures that use a 64-bit time_t. > > This interface is problematic for y2038, when time_t overflows on 32-bit > architectures, but the plan so far is that a libc with 64-bit time_t > will not call into the gettimeofday() vdso helper at all, and only > have a method for entering clock_gettime(). This means we don't have > to fix it here, though we probably want to add a new clock_gettime() > entry point using a 64-bit version of 'struct timespec' at some point. > > Changing the vdso code to use __kernel_old_timeval helps isolate > this usage from the other ones that still need to be fixed properly, > and it gets us closer to removing the 'timeval' definition from the > kernel sources. > > Signed-off-by: Arnd Bergmann Reviewed-by: Thomas Gleixner