Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps

2016-06-14 Thread Deepa Dinamani
On Fri, Jun 10, 2016 at 3:19 PM, Arnd Bergmann wrote: > On Thursday, June 9, 2016 11:45:01 AM CEST Linus Torvalds wrote: >> On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani >> wrote: >> > CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. >> >

Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps

2016-06-10 Thread Arnd Bergmann
On Thursday, June 9, 2016 11:45:01 AM CEST Linus Torvalds wrote: > On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani > wrote: > > CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. > > current_fs_time() will be transitioned to be y2038 safe > > along with vfs. > > > >

Re: [Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps

2016-06-09 Thread Linus Torvalds
On Wed, Jun 8, 2016 at 10:04 PM, Deepa Dinamani wrote: > CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. > current_fs_time() will be transitioned to be y2038 safe > along with vfs. > > current_fs_time() returns timestamps according to the > granularities set in the

[Y2038] [PATCH 02/21] fs: ext4: Use current_fs_time() for inode timestamps

2016-06-08 Thread Deepa Dinamani
CURRENT_TIME_SEC and CURRENT_TIME are not y2038 safe. current_fs_time() will be transitioned to be y2038 safe along with vfs. current_fs_time() returns timestamps according to the granularities set in the super_block. The granularity check to call current_fs_time() or CURRENT_TIME_SEC is not