From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 00/25] Change time_t and clock_t to 64 bit Date: Fri, 16 May 2014 16:06:15 -0700 Message-ID: <537699E7.9050005@zytor.com> References: <1399971456-3941-1-git-send-email-lftan@altera.com> <8468354.y2kUZdOz9e@wuerfel> <1400168823.7862.9.camel@dabdike> <9176609.NChAu49t7f@wuerfel> <20140515220717.1ced0f1a@alan.etchedpixels.co.uk> <20140516074826.GB8555@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20140516074826.GB8555@infradead.org> Sender: linux-kernel-owner@vger.kernel.org To: Christoph Hellwig , One Thousand Gnomes Cc: Arnd Bergmann , James Bottomley , Geert Uytterhoeven , Thomas Gleixner , Ley Foon Tan , Linux-Arch , "linux-kernel@vger.kernel.org" , LeyFoon Tan , Chung-Lin Tang List-Id: linux-arch.vger.kernel.org On 05/16/2014 12:48 AM, Christoph Hellwig wrote: > > The stat(64) syscall already has stopped time_t for a long time: > > struct stat64 { > ... > int st_atime; /* Time of last access. */ > unsigned int st_atime_nsec; > int st_mtime; /* Time of last modification. */ > unsigned int st_mtime_nsec; > int st_ctime; /* Time of last status change. */ > unsigned int st_ctime_nsec; > }; > ... except that that is really a struct timespec just written weirdly, and userspace uses it as a struct timespec. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from terminus.zytor.com ([198.137.202.10]:60744 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756171AbaEPXHS (ORCPT ); Fri, 16 May 2014 19:07:18 -0400 Message-ID: <537699E7.9050005@zytor.com> Date: Fri, 16 May 2014 16:06:15 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 Subject: Re: [PATCH 00/25] Change time_t and clock_t to 64 bit References: <1399971456-3941-1-git-send-email-lftan@altera.com> <8468354.y2kUZdOz9e@wuerfel> <1400168823.7862.9.camel@dabdike> <9176609.NChAu49t7f@wuerfel> <20140515220717.1ced0f1a@alan.etchedpixels.co.uk> <20140516074826.GB8555@infradead.org> In-Reply-To: <20140516074826.GB8555@infradead.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-arch-owner@vger.kernel.org List-ID: To: Christoph Hellwig , One Thousand Gnomes Cc: Arnd Bergmann , James Bottomley , Geert Uytterhoeven , Thomas Gleixner , Ley Foon Tan , Linux-Arch , "linux-kernel@vger.kernel.org" , LeyFoon Tan , Chung-Lin Tang Message-ID: <20140516230615.b8RqkNBU2yCD51o7mwwEMGlsUUBTmYir9OXbIsy-nQg@z> On 05/16/2014 12:48 AM, Christoph Hellwig wrote: > > The stat(64) syscall already has stopped time_t for a long time: > > struct stat64 { > ... > int st_atime; /* Time of last access. */ > unsigned int st_atime_nsec; > int st_mtime; /* Time of last modification. */ > unsigned int st_mtime_nsec; > int st_ctime; /* Time of last status change. */ > unsigned int st_ctime_nsec; > }; > ... except that that is really a struct timespec just written weirdly, and userspace uses it as a struct timespec. -hpa