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

2016-06-24 Thread Deepa Dinamani
>> @@ -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: [Y2038] [PATCH v2 07/24] fs: ubifs: Replace CURRENT_TIME_SEC with current_time

2016-06-24 Thread Deepa Dinamani
>> @@ -84,6 +84,8 @@ static int create_default_filesystem(struct ubifs_info *c) >> int min_leb_cnt = UBIFS_MIN_LEB_CNT; >> long long tmp64, main_bytes; >> __le64 tmp_le64; >> + __le32 tmp_le32; >> + struct timespec ts; >> >> /* Some functions called from

Re: [Y2038] Fourth draft of the Y2038 design document

2016-06-24 Thread Arnd Bergmann
On Thursday, June 23, 2016 4:56:00 PM CEST Joseph Myers wrote: > On Thu, 23 Jun 2016, Arnd Bergmann wrote: > > > Is there a policy about what justifies such an ABI break? I.e. is it > > The clear implication from the discussions around C++11 support in > libstdc++, which resulted in the