From: Jeff Layton <jlayton@primarydata.com>
Date: Wed, 30 Jul 2014 01:34:27 +0000 (-0400)
Subject: nfsd: Add a mutex to protect the NFSv4.0 open owner replay cache
X-Git-Tag: omap-for-v3.17/fixes-against-rc2~101^2~57
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=58fb12e6a42f30adf209f8f41385a3bbb2c82420;p=pandora-kernel.git

nfsd: Add a mutex to protect the NFSv4.0 open owner replay cache

We don't want to rely on the client_mutex for protection in the case of
NFSv4 open owners. Instead, we add a mutex that will only be taken for
NFSv4.0 state mutating operations, and that will be released once the
entire compound is done.

Also, ensure that nfsd4_cstate_assign_replay/nfsd4_cstate_clear_replay
take a reference to the stateowner when they are using it for NFSv4.0
open and lock replay caching.

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
---

Reading git-diff-tree failed