On Wed 08-06-16 22:04:45, Deepa Dinamani wrote:
CURRENT_TIME_SEC is not y2038 safe. current_fs_time() will be transitioned to use 64 bit time along with vfs in a separate patch. There is no plan to transistion CURRENT_TIME_SEC to use y2038 safe time interfaces.
current_fs_time() will also be extended to use superblock range checking parameters when range checking is introduced.
This works because alloc_super() fills in the the s_time_gran in super block to NSEC_PER_SEC.
Also note that filesystem specific times like the birthtime, creation time that were using same interfaces to obtain time retain same logistics.
You create line longer than 80 characters for affs and reiserfs. Please wrap those lines properly. Other than that feel free to add:
Acked-by: Jan Kara jack@suse.cz
Honza