summaryrefslogtreecommitdiffstats
path: root/fs/nfs/nfs4_fs.h
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2019-11-05 11:04:13 -0500
committerTrond Myklebust <trond.myklebust@hammerspace.com>2019-11-18 11:04:32 +0100
commit21f86d2d63f9b0c10a3bd369ce8c97f1f786be53 (patch)
treee3984e7e2e7c4e0265525b6888093f6de83a1caa /fs/nfs/nfs4_fs.h
parent511ba52e4c01fd1878140774e6215e0de6c2f36f (diff)
downloadlinux-21f86d2d63f9b0c10a3bd369ce8c97f1f786be53.tar.gz
linux-21f86d2d63f9b0c10a3bd369ce8c97f1f786be53.tar.bz2
linux-21f86d2d63f9b0c10a3bd369ce8c97f1f786be53.zip
NFS4: Trace lock reclaims
One of the most frustrating messages our sustaining team sees is the "Lock reclaim failed!" message. Add some observability in the client's lock reclaim logic so we can capture better data the first time a problem occurs. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'fs/nfs/nfs4_fs.h')
-rw-r--r--fs/nfs/nfs4_fs.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/nfs/nfs4_fs.h b/fs/nfs/nfs4_fs.h
index a4520115d8a3..a7a73b1d1fec 100644
--- a/fs/nfs/nfs4_fs.h
+++ b/fs/nfs/nfs4_fs.h
@@ -166,11 +166,9 @@ enum {
NFS_STATE_RECOVERY_FAILED, /* OPEN stateid state recovery failed */
NFS_STATE_MAY_NOTIFY_LOCK, /* server may CB_NOTIFY_LOCK */
NFS_STATE_CHANGE_WAIT, /* A state changing operation is outstanding */
-#ifdef CONFIG_NFS_V4_2
NFS_CLNT_DST_SSC_COPY_STATE, /* dst server open state on client*/
NFS_CLNT_SRC_SSC_COPY_STATE, /* src server open state on client*/
NFS_SRV_SSC_COPY_STATE, /* ssc state on the dst server */
-#endif /* CONFIG_NFS_V4_2 */
};
struct nfs4_state {