[PATCH] nfsd: nfs_replay_me

We are using NFS_REPLAY_ME as a special error value that is never leaked to
clients.  That works fine; the only problem is mixing host- and network-
endian values in the same objects.  Network-endian equivalent would work just
as fine; switch to it.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Acked-by: Trond Myklebust <trond.myklebust@fys.uio.no>
Acked-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index 2e468c9e64d9..293b6495829f 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -1477,7 +1477,7 @@ nfsd4_process_open1(struct nfsd4_open *open)
         }
         if (open->op_seqid == sop->so_seqid - 1) {
                 if (sop->so_replay.rp_buflen)
-                        return NFSERR_REPLAY_ME;
+                        return nfserr_replay_me;
                 /* The original OPEN failed so spectacularly
                  * that we don't even have replay data saved!
                  * Therefore, we have no choice but to continue
@@ -2233,7 +2233,7 @@ check_replay:
         if (seqid == sop->so_seqid - 1) {
                 dprintk("NFSD: preprocess_seqid_op: retransmission?\n");
                 /* indicate replay to calling function */
-                return NFSERR_REPLAY_ME;
+                return nfserr_replay_me;
         }
         printk("NFSD: preprocess_seqid_op: bad seqid (expected %d, got %d)\n",
                         sop->so_seqid, seqid);