[RFC 00/32] making inode time stamps y2038 ready
Arnd Bergmann
arnd at arndb.de
Tue Jun 3 06:21:29 MDT 2014
On Saturday 31 May 2014 18:30:49 Vyacheslav Dubeyko wrote:
> By the way, what about NILFS2? Is NILFS2 ready for suggested approach
> without any changes?
nilfs2 and a lot of other file systems don't need any changes for
this, because they don't assign the inode time stamp fields to
a 'struct timespec'.
FWIW, nilfs2 uses a 64-bit seconds value, which is always safe and
can represent the full range of user space timespec on all machines.
Arnd
More information about the samba-technical
mailing list