CURRENT_TIME_SEC is not y2038 safe.
Replace use of CURRENT_TIME_SEC with ktime_get_real_seconds
in segment timestamps used by GC algorithm including the
segment mtime timestamps.
Signed-off-by: Deepa Dinamani
Cc: Jaegeuk Kim
Cc: Changman Lee
Cc: linux-f2fs-devel@lists.sourceforge.net
---
fs/f
On Saturday, June 25, 2016 2:37:24 PM CEST Deepa Dinamani wrote:
> The series is aimed at getting rid of CURRENT_TIME, CURRENT_TIME_SEC macros
> and replacing current_fs_time() with current_time().
> The macros are not y2038 safe. There is no plan to transition them into being
> y2038 safe.
> ktime
The series is aimed at getting rid of CURRENT_TIME, CURRENT_TIME_SEC macros
and replacing current_fs_time() with current_time().
The macros are not y2038 safe. There is no plan to transition them into being
y2038 safe.
ktime_get_* api's can be used in their place. And, these are y2038 safe.
CURREN
Hi Jaegeuk,
Sorry please ignore this one -- it looks like false warning from old
gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered
thousands of these warnings..
Thanks,
Fengguang
On Tue, Jul 19, 2016 at 10:52:50PM +0800, kbuild test robot wrote:
>tree: https://git.kernel.org/pub/