[PATCH 10/16] nfsd4: remove spurious replay_owner check
J. Bruce Fields
bfields at fieldses.org
Fri Dec 1 14:41:08 EST 2006
From: J. Bruce Fields <bfields at fieldses.org>
OK, this is embarassing--I've even looked back at the history, and cannot
for the life of me figure out why I added this check.
Signed-off-by: J. Bruce Fields <bfields at citi.umich.edu>
---
fs/nfsd/nfs4proc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
index 1aa1897..22cdb68 100644
--- a/fs/nfsd/nfs4proc.c
+++ b/fs/nfsd/nfs4proc.c
@@ -959,7 +959,7 @@ encode_op:
nfsd4_encode_operation(resp, op);
status = op->status;
}
- if (replay_owner && (replay_owner != (void *)(-1))) {
+ if (replay_owner) {
nfs4_put_stateowner(replay_owner);
replay_owner = NULL;
}
More information about the NFSv4
mailing list