diff options
author | Arnd Bergmann <arnd@arndb.de> | 2019-11-04 16:31:52 +0100 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2019-12-19 22:07:17 -0500 |
commit | 20b7d86f29d39e8ae19bb29c24ffee70dc385ddf (patch) | |
tree | f364c2f6a1a9fed9a9bc8cdc0673381e29cf596b /Documentation/security | |
parent | 9594497f2c78993cb66b696122f7c65528ace985 (diff) | |
download | linux-20b7d86f29d39e8ae19bb29c24ffee70dc385ddf.tar.bz2 |
nfsd: use boottime for lease expiry calculation
A couple of time_t variables are only used to track the state of the
lease time and its expiration. The code correctly uses the 'time_after()'
macro to make this work on 32-bit architectures even beyond year 2038,
but the get_seconds() function and the time_t type itself are deprecated
as they behave inconsistently between 32-bit and 64-bit architectures
and often lead to code that is not y2038 safe.
As a minor issue, using get_seconds() leads to problems with concurrent
settimeofday() or clock_settime() calls, in the worst case timeout never
triggering after the time has been set backwards.
Change nfsd to use time64_t and ktime_get_boottime_seconds() here. This
is clearly excessive, as boottime by itself means we never go beyond 32
bits, but it does mean we handle this correctly and consistently without
having to worry about corner cases and should be no more expensive than
the previous implementation on 64-bit architectures.
The max_cb_time() function gets changed in order to avoid an expensive
64-bit division operation, but as the lease time is at most one hour,
there is no change in behavior.
Also do the same for server-to-server copy expiration time.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
[bfields@redhat.com: fix up copy expiration]
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'Documentation/security')
0 files changed, 0 insertions, 0 deletions