Re: [Y2038] [RFC 02/15] vfs: Change all structures to support 64 bit time

2016-01-12 Thread Dave Chinner
On Mon, Jan 11, 2016 at 09:42:36PM -0800, Deepa Dinamani wrote: > > On Jan 11, 2016, at 04:33, Dave Chinner wrote: > > > >> On Wed, Jan 06, 2016 at 09:35:59PM -0800, Deepa Dinamani wrote: > >> The current representation of inode times in struct inode, struct iattr, > >> and struct kstat use struct

Re: [Y2038] [RFC 02/15] vfs: Change all structures to support 64 bit time

2016-01-12 Thread Arnd Bergmann
On Tuesday 12 January 2016 19:29:57 Dave Chinner wrote: > > This is what I meant about premature optimisation - you've got a > wonderfully complex solution to a problem that we don't need to > solve to support timestamps >y2038. It's also why it goes down the > wrong path at this point - most of t

Re: [Y2038] [PATCH v2] isdn: divamnt: use y2038 safe time structures and functions

2016-01-12 Thread Arnd Bergmann
On Friday 08 January 2016 09:47:39 Alison Schofield wrote: > divamnt stores a start_time at module init and uses it to calculate > elapsed time. That elapsed time, stored in secs and usecs, is part of > the trace data the driver maintains for the DIVA Server ISDN cards. > No change to the format of

Re: [Y2038] [RFC 02/15] vfs: Change all structures to support 64 bit time

2016-01-12 Thread Dave Chinner
On Tue, Jan 12, 2016 at 10:27:07AM +0100, Arnd Bergmann wrote: > On Tuesday 12 January 2016 19:29:57 Dave Chinner wrote: > > > > This is what I meant about premature optimisation - you've got a > > wonderfully complex solution to a problem that we don't need to > > solve to support timestamps >y20