[f2fs-dev] [PATCH v3 14/24] fs: f2fs: Use ktime_get_real_seconds for sit_info times

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

Re: [f2fs-dev] [Y2038] [PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()

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

[f2fs-dev] [PATCH v3 00/24] Delete CURRENT_TIME_SEC and replace current_fs_time()

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

Re: [f2fs-dev] [kbuild-all] [f2fs:dev-test 63/64] fs/ext4/readpage.o: warning: objtool: mpage_end_io()+0x53: function has unreachable instruction

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/