[Y2038] [PATCH v2 23/24] time: Delete CURRENT_TIME_SEC and CURRENT_TIME macro

All uses of these macros have been replaced by other time functions. These macros are also not y2038 safe. And, all its use cases can be fulfilled by y2038 safe ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas

[Y2038] [PATCH v2 24/24] time: Delete current_fs_time() function

All uses of the current_fs_time() function have been replaced by other time interfaces. And, its use cases can be fulfilled by current_time() or ktime_get_* variants. Signed-off-by: Deepa Dinamani Cc: John Stultz Cc: Thomas Gleixner

[Y2038] [PATCH v2 19/24] fnic: Use time64_t to represent trace timestamps

trace timestamps use struct timespec and CURRENT_TIME which are not y2038 safe. These timestamps are only part of the trace log on the machine and are not shared with the fnic. Replace then with y2038 safe struct timespec64 and ktime_get_real_ts64(), respectively. Note that change to add

[Y2038] [PATCH v2 21/24] libceph: Replace CURRENT_TIME with ktime_get_real_ts

CURRENT_TIME is not y2038 safe. The macro will be deleted and all the references to it will be replaced by ktime_get_* apis. struct timespec is also not y2038 safe. Retain timespec for timestamp representation here as ceph uses it internally everywhere. These references will be changed to use

[Y2038] [PATCH v2 15/24] fs: ocfs2: Use time64_t to represent orphan scan times

struct timespec is not y2038 safe. Use time64_t which is y2038 safe to represent orphan scan times. time64_t is sufficient here as only the seconds delta times are relevant. Also use appropriate time functions that return time in time64_t format. Time functions now return monotonic time instead

[Y2038] [PATCH v2 18/24] fs: nfs: Make nfs boot time y2038 safe

boot_time is represented as a struct timespec. struct timespec and CURRENT_TIME are not y2038 safe. Overall, the plan is to use timespec64 and ktime_t for all internal kernel representation of timestamps. CURRENT_TIME will also be removed. boot_time is used to construct the nfs client boot

[Y2038] [PATCH v2 08/24] fs: btrfs: Use ktime_get_real_ts for root ctime

btrfs_root_item maintains the ctime for root updates. This is not part of vfs_inode. Since current_time() uses struct inode* as an argument as Linus suggested, this cannot be used to update root times unless, we modify the signature to use inode. Since btrfs uses nanosecond time granularity, it

[Y2038] [PATCH v2 04/24] fs: Replace current_fs_time() with current_time()

current_fs_time() uses struct super_block* as an argument. As per Linus's suggestion, this is changed to take struct inode* as a parameter instead. This is because the function is primarily meant for vfs inode timestamps. Also the function was renamed as per Arnd's suggestion. Change all calls to

[Y2038] [PATCH v2 05/24] fs: jfs: Replace CURRENT_TIME_SEC by current_time()

jfs uses nanosecond granularity for filesystem timestamps. Only this assignemt is not using nanosecond granularity. Use current_time() to get the right granularity. Signed-off-by: Deepa Dinamani Cc: Dave Kleikamp Cc:

Re: [Y2038] [PATCH] quota: use time64_t internally

On Fri 17-06-16 22:03:16, Arnd Bergmann wrote: > The quota subsystem has two formats, the old v1 format using architecture > specific time_t values on the on-disk format, while the v2 format > (introduced in Linux 2.5.16 and 2.4.22) uses fixed 64-bit little-endian. > > While there is no future