diff options
| author | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-08-25 22:09:08 -0400 |
|---|---|---|
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | 2014-08-26 16:17:48 -0400 |
| commit | 412f6c4c26fb1eba8844290663837561ac53fa6e (patch) | |
| tree | 51fedde9765c9060328cd2d190cc634784234bf2 /fs/nfs/nfs3acl.c | |
| parent | aee7af356e151494d5014f57b33460b162f181b5 (diff) | |
| download | blackbird-op-linux-412f6c4c26fb1eba8844290663837561ac53fa6e.tar.gz blackbird-op-linux-412f6c4c26fb1eba8844290663837561ac53fa6e.zip | |
NFSv4: Don't clear the open state when we just did an OPEN_DOWNGRADE
If we did an OPEN_DOWNGRADE, then the right thing to do on success, is
to apply the new open mode to the struct nfs4_state. Instead, we were
unconditionally clearing the state, making it appear to our state
machinery as if we had just performed a CLOSE.
Fixes: 226056c5c312b (NFSv4: Use correct locking when updating nfs4_state...)
Cc: stable@vger.kernel.org # 3.15+
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Diffstat (limited to 'fs/nfs/nfs3acl.c')
0 files changed, 0 insertions, 0 deletions
