On Thu, Oct 19, 2017 at 02:34:20PM -0400, Olga Kornievskaia wrote:
> On Thu, Oct 19, 2017 at 2:17 PM, J. Bruce Fields <bfields@xxxxxxxxxx> wrote:
> > On Thu, Oct 19, 2017 at 01:21:46PM -0400, Olga Kornievskaia wrote:
> >> On Wed, Oct 18, 2017 at 5:25 PM, J. Bruce Fields <bfields@xxxxxxxxxx> wrote:
> >> > From: "J. Bruce Fields" <bfields@xxxxxxxxxx>
> >> >
> >> > Currently our handling of 4.1+ requests without "cachethis" set is
> >> > confusing and not quite correct.
> >> >
> >> > Suppose a client sends a compound consisting of only a single SEQUENCE
> >> > op, and it matches the seqid in a session slot (so it's a retry), but
> >> > the previous request with that seqid did not have "cachethis" set.
> >> >
> >> > The obvious thing to do might be to return NFS4ERR_RETRY_UNCACHED_REP,
> >> > but the protocol only allows that to be returned on the op following the
> >> > SEQUENCE, and there is no such op in this case.
> >> >
> >> > The protocol permits us to cache replies even if the client didn't ask
> >> > us to. And it's easy to do so in the case of solo SEQUENCE compounds.
> >> >
> >> > So, when we get a solo SEQUENCE, we can either return the previously
> >> > cached reply or NFSERR_SEQ_FALSE_RETRY if we notice it differs in some
> >> > way from the original call.
> >>
> >> I'm confused in my testing the error was SEQ_MISORDERED and not
> >> SEQ_FALSE_RETRY error?
> >
> > Yes, I must have a typo somewhere, but I haven't spotted it yet. That
> > was with both patches applied?
>
> Yes both patches.
Some days I wonder if I should just turn in my C programmer card.
--b.
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index 7bd3ad88b85c..8aeda6ad15b9 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -2294,7 +2294,7 @@ nfsd4_store_cache_entry(struct nfsd4_compoundres *resp)
slot->sl_flags |= NFSD4_SLOT_INITIALIZED;
if (!nfsd4_cache_this(resp)) {
- slot->sl_flags &= !NFSD4_SLOT_CACHED;
+ slot->sl_flags &= ~NFSD4_SLOT_CACHED;
return;
}
slot->sl_flags |= NFSD4_SLOT_CACHED;
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
