nfsd: fix setting of NFS4_OO_CONFIRMED in nfsd4_open
authorJeff Layton <jlayton@primarydata.com>
Fri, 30 May 2014 13:09:28 +0000 (09:09 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Wed, 4 Jun 2014 19:42:02 +0000 (15:42 -0400)
commitba5378b66f5eb20e464796c5b088c0961fb5f618
tree8fafd0f7135dbfdc824f3e1ecd9528199a2a6ad4
parent931ee56c67573eb4e51c8a4e78598d965b8b059e
nfsd: fix setting of NFS4_OO_CONFIRMED in nfsd4_open

In the NFS4_OPEN_CLAIM_PREVIOUS case, we should only mark it confirmed
if the nfs4_check_open_reclaim check succeeds.

In the NFS4_OPEN_CLAIM_DELEG_PREV_FH and NFS4_OPEN_CLAIM_DELEGATE_PREV
cases, I see no point in declaring the openowner confirmed when the
operation is going to fail anyway, and doing so might allow the client
to game things such that it wouldn't need to confirm a subsequent open
with the same owner.

Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4proc.c