[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6347520.8jMPlVsFjM@wuerfel>
Date: Sat, 31 May 2014 17:23:02 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Richard Cochran <richardcochran@...il.com>
Cc: linux-kernel@...r.kernel.org, hch@...radead.org,
linux-mtd@...ts.infradead.org, hpa@...or.com, logfs@...fs.org,
linux-afs@...ts.infradead.org, joseph@...esourcery.com,
linux-arch@...r.kernel.org, linux-cifs@...r.kernel.org,
linux-scsi@...r.kernel.org, ceph-devel@...r.kernel.org,
codalist@...a.cs.cmu.edu, cluster-devel@...hat.com,
coda@...cmu.edu, geert@...ux-m68k.org, linux-ext4@...r.kernel.org,
fuse-devel@...ts.sourceforge.net, reiserfs-devel@...r.kernel.org,
xfs@....sgi.com, john.stultz@...aro.org, tglx@...utronix.de,
linux-nfs@...r.kernel.org, linux-ntfs-dev@...ts.sourceforge.net,
samba-technical@...ts.samba.org,
linux-f2fs-devel@...ts.sourceforge.net, ocfs2-devel@....oracle.com,
linux-fsdevel@...r.kernel.org, lftan@...era.com,
linux-btrfs@...r.kernel.org
Subject: Re: [RFC 00/32] making inode time stamps y2038 ready
On Saturday 31 May 2014 16:51:15 Richard Cochran wrote:
> On Fri, May 30, 2014 at 10:01:24PM +0200, Arnd Bergmann wrote:
> >
> > I picked this because it is a fairly isolated problem, as the
> > inode time stamps are rarely assigned to any other time values.
> > As a byproduct of this work, I documented for each of the file
> > systems we support how long the on-disk format can work[1].
>
> Why are some of the time stamp expiration dates marked as "never"?
It's an approximation:
with 64-bit timestamps, you can represent close to 300 billion
years, which is way past the time that our planet can sustain
life of any form[1].
Arnd
[1] http://en.wikipedia.org/wiki/Timeline_of_the_far_future
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists