Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

>> @@ -3727,6 +3727,7 @@ static int ext4_cross_rename(struct inode *old_dir, >> struct dentry *old_dentry, >> }; >> u8 new_file_type; >> int retval; >> + struct timespec ctime; >> >> if ((ext4_encrypted_inode(old_dir) || >>

Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

>> @@ -3727,6 +3727,7 @@ static int ext4_cross_rename(struct inode *old_dir, >> struct dentry *old_dentry, >> }; >> u8 new_file_type; >> int retval; >> + struct timespec ctime; >> >> if ((ext4_encrypted_inode(old_dir) || >>

Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

On Sunday, June 19, 2016 5:27:05 PM CEST Deepa Dinamani wrote: > @@ -3727,6 +3727,7 @@ static int ext4_cross_rename(struct inode *old_dir, > struct dentry *old_dentry, > }; > u8 new_file_type; > int retval; > + struct timespec ctime; > > if

Re: [PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

On Sunday, June 19, 2016 5:27:05 PM CEST Deepa Dinamani wrote: > @@ -3727,6 +3727,7 @@ static int ext4_cross_rename(struct inode *old_dir, > struct dentry *old_dentry, > }; > u8 new_file_type; > int retval; > + struct timespec ctime; > > if

[PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. current_time() will be transitioned to be y2038 safe along with vfs. current_time() returns timestamps according to the granularities set in the super_block. The granularity check in ext4_current_time() to call current_time() or

[PATCH v2 06/24] fs: ext4: Use current_time() for inode timestamps

CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. current_time() will be transitioned to be y2038 safe along with vfs. current_time() returns timestamps according to the granularities set in the super_block. The granularity check in ext4_current_time() to call current_time() or