nfsd: handle nfs3 timestamps as unsigned
authorArnd Bergmann <arnd@arndb.de>
Thu, 31 Oct 2019 13:55:32 +0000 (14:55 +0100)
committerJ. Bruce Fields <bfields@redhat.com>
Thu, 19 Dec 2019 22:46:08 +0000 (17:46 -0500)
commit92c5e46911c0c1b20fa2294298aaf008c3afe975
tree778b8208d025275dc29128be199efc0614c080f7
parente29f470396a7447764e73289fd63a4591a0b443b
nfsd: handle nfs3 timestamps as unsigned

The decode_time3 function behaves differently on 32-bit
and 64-bit architectures: on the former, a 32-bit timestamp
gets converted into an signed number and then into a timestamp
between 1902 and 2038, while on the latter it is interpreted
as unsigned in the range 1970-2106.

Change all the remaining 'timespec' in nfsd to 'timespec64'
to make the behavior the same, and use the current interpretation
of the dominant 64-bit architectures.

Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs3xdr.c
fs/nfsd/nfsfh.h