From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
joseph@codesourcery.com, john.stultz@linaro.org,
hch@infradead.org, tglx@linutronix.de, geert@linux-m68k.org,
lftan@altera.com, hpa@zytor.com, linux-fsdevel@vger.kernel.org,
ceph-devel@vger.kernel.org, cluster-devel@redhat.com,
coda@cs.cmu.edu, codalist@TELEMANN.coda.cs.cmu.edu,
fuse-devel@lists.sourceforge.net, linux-afs@lists.infradead.org,
linux-btrfs@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, linux-scsi@vger.kernel.org,
logfs@logfs.org, ocfs2-devel@oss.oracle.com,
reiserfs-devel@vger.kernel.org, samba-technical@lists.samba.org,
xfs@oss.sgi.com
Subject: Re: [RFC 00/32] making inode time stamps y2038 ready
Date: Sat, 31 May 2014 18:30:49 +0400 [thread overview]
Message-ID: <1401546649.2413.6.camel@slavad-CELSIUS-H720> (raw)
In-Reply-To: <1401480116-1973111-1-git-send-email-arnd@arndb.de>
Hi Arnd,
On Fri, 2014-05-30 at 22:01 +0200, Arnd Bergmann wrote:
[snip]
>
> Arnd Bergmann (32):
> fs: introduce new 'struct inode_time'
> uapi: add struct __kernel_timespec{32,64}
> fs: introduce sys_utimens64at
> fs: introduce sys_newfstat64/sys_newfstatat64
> arch: hook up new stat and utimes syscalls
> isofs: fix timestamps beyond 2027
> fs/nfs: convert to struct inode_time
> fs/ceph: convert to 'struct inode_time'
> fs/pstore: convert to struct inode_time
> fs/coda: convert to struct inode_time
> xfs: convert to struct inode_time
> btrfs: convert to struct inode_time
> ext3: convert to struct inode_time
> ext4: convert to struct inode_time
> cifs: convert to struct inode_time
> ntfs: convert to struct inode_time
> ubifs: convert to struct inode_time
> ocfs2: convert to struct inode_time
> fs/fat: convert to struct inode_time
> afs: convert to struct inode_time
> udf: convert to struct inode_time
> fs: convert simple fs to inode_time
> logfs: convert to struct inode_time
> hfs, hfsplus: convert to struct inode_time
> gfs2: convert to struct inode_time
> reiserfs: convert to struct inode_time
> jffs2: convert to struct inode_time
> adfs: convert to struct inode_time
> f2fs: convert to struct inode_time
> fuse: convert to struct inode_time
> scsi: fnic: use current_kernel_time() for timestamp
> fs: use new inode_time definition unconditionally
>
By the way, what about NILFS2? Is NILFS2 ready for suggested approach
without any changes?
Thanks,
Vyacheslav Dubeyko.
next prev parent reply other threads:[~2014-05-31 14:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 20:01 [RFC 00/32] making inode time stamps y2038 ready Arnd Bergmann
2014-05-30 20:01 ` [RFC 12/32] btrfs: convert to struct inode_time Arnd Bergmann
2014-05-31 14:30 ` Vyacheslav Dubeyko [this message]
2014-06-03 12:21 ` [RFC 00/32] making inode time stamps y2038 ready Arnd Bergmann
2014-05-31 14:51 ` Richard Cochran
2014-05-31 15:23 ` Arnd Bergmann
2014-05-31 18:22 ` Richard Cochran
2014-05-31 19:34 ` H. Peter Anvin
2014-06-01 4:46 ` Richard Cochran
2014-06-01 4:44 ` Richard Cochran
2014-06-02 13:52 ` Joseph S. Myers
2014-06-02 19:19 ` Arnd Bergmann
2014-06-02 19:26 ` H. Peter Anvin
2014-06-02 19:55 ` Arnd Bergmann
2014-06-02 21:57 ` H. Peter Anvin
2014-06-03 14:22 ` Arnd Bergmann
2014-06-03 14:33 ` Joseph S. Myers
2014-06-03 14:37 ` Arnd Bergmann
2014-06-03 21:38 ` Dave Chinner
2014-06-04 15:03 ` Arnd Bergmann
2014-06-04 17:30 ` Nicolas Pitre
2014-06-04 19:24 ` Arnd Bergmann
2014-06-05 0:10 ` H. Peter Anvin
2014-06-10 9:54 ` Arnd Bergmann
2014-06-02 21:02 ` Joseph S. Myers
2014-06-04 15:05 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1401546649.2413.6.camel@slavad-CELSIUS-H720 \
--to=slava@dubeyko.com \
--cc=arnd@arndb.de \
--cc=ceph-devel@vger.kernel.org \
--cc=cluster-devel@redhat.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@TELEMANN.coda.cs.cmu.edu \
--cc=fuse-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=joseph@codesourcery.com \
--cc=lftan@altera.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=linux-scsi@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=tglx@linutronix.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).