| To: | Arnd Bergmann <arnd@xxxxxxxx> |
|---|---|
| Subject: | Re: [RFC 00/32] making inode time stamps y2038 ready |
| From: | Richard Cochran <richardcochran@xxxxxxxxx> |
| Date: | Sat, 31 May 2014 16:51:15 +0200 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, hch@xxxxxxxxxxxxx, linux-mtd@xxxxxxxxxxxxxxxxxxx, hpa@xxxxxxxxx, logfs@xxxxxxxxx, linux-afs@xxxxxxxxxxxxxxxxxxx, joseph@xxxxxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx, linux-cifs@xxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, ceph-devel@xxxxxxxxxxxxxxx, codalist@xxxxxxxxxxxxxxx, cluster-devel@xxxxxxxxxx, coda@xxxxxxxxxx, geert@xxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, fuse-devel@xxxxxxxxxxxxxxxxxxxxx, reiserfs-devel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, john.stultz@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-nfs@xxxxxxxxxxxxxxx, linux-ntfs-dev@xxxxxxxxxxxxxxxxxxxxx, samba-technical@xxxxxxxxxxxxxxx, linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx, ocfs2-devel@xxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, lftan@xxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=m/qDo/jw5RnGAKXBa93qC3zg8NxD5t1PV6+cH65dS2k=; b=0OcZgSFKhg/qmpgOdGBSX3on7TtSxchva/lErbcWlj5KtOeaeXYT74/38VE9k/yvIb zO+z8vy76v1GVshivwLEoOO95nKgQRddfRvlF0FMWfs5LZ0vaXj1F03YpqKiPNjhf0qm LSaNOFOXmiZkfzjcg3Vhs4Gv66bmpwChFeYVrMP1gQZygdJTFgD7sJ+uYmiBLqc4Qs1+ /1Dyzs7+QmhGfzURu0XJzAiJr1MMhrzoYDlVKcTO0MkCUu2RklAl1mxvS96zb8iepi/u IvE5b4DzgtX1mAC/OVguR8VmTPukv5lqM5KlumKMXJMlrm9vOvcB3xGY5X3GuyVgBsum kXhg== |
| In-reply-to: | <1401480116-1973111-1-git-send-email-arnd@xxxxxxxx> |
| References: | <1401480116-1973111-1-git-send-email-arnd@xxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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"? Thanks, Richard |
| Previous by Date: | Re: [RFC 00/32] making inode time stamps y2038 ready, Vyacheslav Dubeyko |
|---|---|
| Next by Date: | Re: [RFC 11/32] xfs: convert to struct inode_time, Arnd Bergmann |
| Previous by Thread: | Re: [RFC 00/32] making inode time stamps y2038 ready, Vyacheslav Dubeyko |
| Next by Thread: | Re: [RFC 00/32] making inode time stamps y2038 ready, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |