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 deepa.kernel@gmail.com Cc: David Sterba dsterba@suse.com
for the btrfs bits
Reviewed-by: David Sterba dsterba@suse.com