diff options
| author | Donald Buczek <buczek@molgen.mpg.de> | 2019-07-07 22:26:10 +0300 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@hammerspace.com> | 2019-07-13 18:48:41 +0300 |
| commit | 5b596830d9710e3554354f717dc56f8640841c82 (patch) | |
| tree | 543274902bbe78d680b57e3ca3d508e901515288 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | ea51efaa9617ee011f53bcd29752c51cda540e06 (diff) | |
| download | linux-5b596830d9710e3554354f717dc56f8640841c82.tar.xz | |
nfs4.0: Refetch lease_time after clientid update
RFC 7530 requires us to refetch the lease time attribute once a new
clientID is established. This is already implemented for the
nfs4.1(+) clients by nfs41_init_clientid, which calls
nfs41_finish_session_reset, which calls nfs4_setup_state_renewal.
To make nfs4_setup_state_renewal available for nfs4.0, move it
further to the top of the source file to include it regardles of
CONFIG_NFS_V4_1 and to save a forward declaration.
Call nfs4_setup_state_renewal from nfs4_init_clientid.
Signed-off-by: Donald Buczek <buczek@molgen.mpg.de>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions