On Fri, Feb 12, 2016 at 01:45:49AM -0800, Deepa Dinamani wrote:
This is in preparation for changing VFS inode timestamps to use 64 bit time. The VFS inode timestamps are not y2038 safe as they use struct timespec. These will be changed to use struct timespec64 instead and that is y2038 safe. But, since the above data type conversion will break the end file systems, use vfs_time functions to access inode times.
current_fs_time() will change along with vfs timestamp data type changes.
xfs_vn_update_time() is a .update callback for inode operations and this needs to change along with vfs inode times.
This code is all different in the current XFS for-next branch. XFS no longer has it's own internal timestamps - it only uses the timestamps in the struct inode now.
Cheers,
Dave.