summaryrefslogtreecommitdiffstats
path: root/fs/nilfs2/btnode.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2018-02-06 15:39:21 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2018-02-06 18:32:45 -0800
commitfb04b91bc2c3a83e9e2ba9c5ce0f0124dd3ffef0 (patch)
tree00e48e16224695ef3eb0cf0b29a57a51a90fea6a /fs/nilfs2/btnode.c
parentca3a45697be3ad59aa8f8f83d0e277b49f4b5680 (diff)
downloadlinux-fb04b91bc2c3a83e9e2ba9c5ce0f0124dd3ffef0.tar.gz
linux-fb04b91bc2c3a83e9e2ba9c5ce0f0124dd3ffef0.tar.bz2
linux-fb04b91bc2c3a83e9e2ba9c5ce0f0124dd3ffef0.zip
nilfs2: use time64_t internally
The superblock and segment timestamps are used only internally in nilfs2 and can be read out using sysfs. Since we are using the old 'get_seconds()' interface and store the data as timestamps, the behavior differs slightly between 64-bit and 32-bit kernels, the latter will show incorrect timestamps after 2038 in sysfs, and presumably fail completely in 2106 as comparisons go wrong. This changes nilfs2 to use time64_t with ktime_get_real_seconds() to handle timestamps, making the behavior consistent and correct on both 32-bit and 64-bit machines. The on-disk format already uses 64-bit timestamps, so nothing changes there. Link: http://lkml.kernel.org/r/20180122211050.1286441-1-arnd@arndb.de Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Cc: Jens Axboe <axboe@kernel.dk> Cc: Ingo Molnar <mingo@kernel.org> Cc: Jan Kara <jack@suse.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/nilfs2/btnode.c')
0 files changed, 0 insertions, 0 deletions