summaryrefslogtreecommitdiffstats
path: root/fs/nfs/nfs4renewd.c
diff options
context:
space:
mode:
authorDonald Buczek <buczek@molgen.mpg.de>2019-07-07 21:26:10 +0200
committerTrond Myklebust <trond.myklebust@hammerspace.com>2019-07-13 11:48:41 -0400
commit5b596830d9710e3554354f717dc56f8640841c82 (patch)
tree543274902bbe78d680b57e3ca3d508e901515288 /fs/nfs/nfs4renewd.c
parentea51efaa9617ee011f53bcd29752c51cda540e06 (diff)
downloadlinux-stable-5b596830d9710e3554354f717dc56f8640841c82.tar.gz
linux-stable-5b596830d9710e3554354f717dc56f8640841c82.tar.bz2
linux-stable-5b596830d9710e3554354f717dc56f8640841c82.zip
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 'fs/nfs/nfs4renewd.c')
0 files changed, 0 insertions, 0 deletions