Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2451395ybc; Wed, 20 Nov 2019 14:34:03 -0800 (PST) X-Google-Smtp-Source: APXvYqxBNEAORy9N4pWLnbetTkkkCXEWuett+xCkZNoDO13yGOJY7xYZDuw2r1UORXzy74K5GjZG X-Received: by 2002:a17:906:3458:: with SMTP id d24mr8624519ejb.271.1574289243650; Wed, 20 Nov 2019 14:34:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574289243; cv=none; d=google.com; s=arc-20160816; b=G6V8AZ4f2JI0Uz5HpEKdRG5N6jS3QoTSuqTKKmHKtNKoyzwKmtk8x0w5dSYCdAJJpN +yiMwtcKtmRiBwIHwVbid6jrGWVYqIOBdgFihEf6u77DMNrsKq0lBh9mHd10JwaB9cse Yz7xhAjhqa3zceHoIYlQCRD1JRtRXfiQE/iDp/dyRxNkbtOCMSQ5e90nVeNtspZnnfJ+ MqkbkYmVqkvaB65mySE946Vjqsv3r82rkLVptx/iSYKUnaSZU9/y5lG2xp38npwqeNNB jJiK1zujYiBBDMQcdAidKm7T230BTKPd+SsF96NTkN0dxdk+WEFK4CrR5QzTISlkJ9TU o99g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:organization:references:in-reply-to:date:cc:to:from :subject:message-id; bh=1U0nU0efA0TUWQmiFthKd9ObP/UY1WCsLDyfjYJT9F0=; b=kxHQGoqK/VlhrXWbgTaycJx4OUo7amv6PbzOZdFCzVa6PoOTojs/CByTbgFU5et9Km tonF3AZ5AqhC3IreAPj4rlLB3iOAqyfTPhPeHTPNVpEwBvSlPfL1WDJH8Ux4EqNvVlpX vFwyQPO+loh2S/Au+6CWaJeKIuOXu7SK89MEybNEp5mPeOphunBigXAIQGXnNNwBKTnu rlkpD1tS2KFqFYe+Qstsl05cX1t2s/ZowdLqwWkng8KU1szzhtpWw2BjHZAJDvNv2hLc XEKXhAYzl+oUwS91Sg7R2ooEIpp674v0eHroKEePpXdai8aTXAS4zFjR4NqvuNow4WDG yViw== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=codethink.co.uk Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e47si636957eda.73.2019.11.20.14.33.39; Wed, 20 Nov 2019 14:34:03 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=codethink.co.uk Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726861AbfKTWaW (ORCPT + 99 others); Wed, 20 Nov 2019 17:30:22 -0500 Received: from imap1.codethink.co.uk ([176.9.8.82]:37120 "EHLO imap1.codethink.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726080AbfKTWaW (ORCPT ); Wed, 20 Nov 2019 17:30:22 -0500 Received: from [167.98.27.226] (helo=xylophone) by imap1.codethink.co.uk with esmtpsa (Exim 4.84_2 #1 (Debian)) id 1iXYUM-00061O-RV; Wed, 20 Nov 2019 22:30:18 +0000 Message-ID: Subject: Re: [Y2038] [PATCH 02/23] y2038: add __kernel_old_timespec and __kernel_old_time_t From: Ben Hutchings To: Arnd Bergmann , y2038@lists.linaro.org Cc: Deepa Dinamani , linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" Date: Wed, 20 Nov 2019 22:30:18 +0000 In-Reply-To: <20191108210824.1534248-2-arnd@arndb.de> References: <20191108210236.1296047-1-arnd@arndb.de> <20191108210824.1534248-2-arnd@arndb.de> Organization: Codethink Ltd. Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-11-08 at 22:07 +0100, Arnd Bergmann wrote: > The 'struct timespec' definition can no longer be part of the uapi headers > because it conflicts with a a now incompatible libc definition. Also, > we really want to remove it in order to prevent new uses from creeping in. > > The same namespace conflict exists with time_t, which should also be > removed. __kernel_time_t could be used safely, but adding 'old' in the > name makes it clearer that this should not be used for new interfaces. > > Add a replacement __kernel_old_timespec structure and __kernel_old_time_t > along the lines of __kernel_old_timeval. [...] > --- a/include/uapi/linux/time_types.h > +++ b/include/uapi/linux/time_types.h > @@ -28,6 +28,11 @@ struct __kernel_old_timeval { > }; > #endif > > +struct __kernel_old_timespec { > + __kernel_time_t tv_sec; /* seconds */ Should this be __kernel_old_time_t for consistency? Ben. > + long tv_nsec; /* nanoseconds */ > +}; > + > struct __kernel_sock_timeval { > __s64 tv_sec; > __s64 tv_usec; -- Ben Hutchings, Software Developer Codethink Ltd https://www.codethink.co.uk/ Dale House, 35 Dale Street Manchester, M1 2HF, United Kingdom