summaryrefslogtreecommitdiffstats
path: root/fs/nfsd/export.h
diff options
context:
space:
mode:
authorJeff Layton <jlayton@primarydata.com>2014-09-12 16:40:21 -0400
committerJ. Bruce Fields <bfields@redhat.com>2014-09-17 16:33:15 -0400
commitd4318acd5d2d34d69a46537f057b20a8f0266e1e (patch)
tree421a5776f63b395dec5d16b5dbbb0217b03dff54 /fs/nfsd/export.h
parent7f5ef2e900d9462bf9cffaf6bb246ed87a20a6d6 (diff)
downloadblackbird-obmc-linux-d4318acd5d2d34d69a46537f057b20a8f0266e1e.tar.gz
blackbird-obmc-linux-d4318acd5d2d34d69a46537f057b20a8f0266e1e.zip
nfsd: pass extra info in env vars to upcalls to allow for early grace period end
In order to support lifting the grace period early, we must tell nfsdcltrack what sort of client the "create" upcall is for. We can't reliably tell if a v4.0 client has completed reclaiming, so we can only lift the grace period once all the v4.1+ clients have issued a RECLAIM_COMPLETE and if there are no v4.0 clients. Also, in order to lift the grace period, we have to tell userland when the grace period started so that it can tell whether a RECLAIM_COMPLETE has been issued for each client since then. Since this is all optional info, we pass it along in environment variables to the "init" and "create" upcalls. By doing this, we don't need to revise the upcall format. The UMH upcall can simply make use of this info if it happens to be present. If it's not then it can just avoid lifting the grace period early. Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Diffstat (limited to 'fs/nfsd/export.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud