Re: [PATCH 04/21] fs: Replace CURRENT_TIME with current_fs_time() for inode timestamps
David Sterba <[email protected]>
| Newsgroups | gmane.linux.kernel.mm,gmane.linux.file-systems,gmane.linux.kernel,gmane.comp.file-systems.pvfs2.devel,gmane.linux.kernel.year-2038,gmane.network.samba.internals,gmane.linux.oprofile,gmane.comp.file-systems.fuse.devel,gmane.linux.file-systems.f2fs,gmane.linux.file-systems.logfs,gmane.comp.file-systems.ocfs2.devel,gmane.linux.cluster.redhat.cluster.devel,gmane.comp.security.selinux,gmane.linux.kernel.autofs,gmane.comp.file-systems.btrfs,gmane.linux.kernel.cifs,gmane.linux.kernel.efi,gmane.linux.nfs,gmane.comp.file-systems.nilfs.user,gmane.linux.drivers.rdma,gmane.linux.kernel.lsm,gmane.linux.usb.general,gmane.linux.network |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jun 08, 2016 at 10:04:48PM -0700, Deepa Dinamani wrote: > CURRENT_TIME macro is not appropriate for filesystems as it > doesn't use the right granularity for filesystem timestamps. > Use current_fs_time() instead. > > CURRENT_TIME is also not y2038 safe. > > This is also in preparation for the patch that transitions > vfs timestamps to use 64 bit time and hence make them > y2038 safe. As part of the effort current_fs_time() will be > extended to do range checks. Hence, it is necessary for all > file system timestamps to use current_fs_time(). Also, > current_fs_time() will be transitioned along with vfs to be > y2038 safe. > > Signed-off-by: Deepa Dinamani <[email protected]> > Cc: David Sterba <[email protected]> for the btrfs bits Reviewed-by: David Sterba <[email protected]> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>