From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: SEQ4_STATUS_ question
Date: Mon, 16 May 2011 15:50:38 -0400 [thread overview]
Message-ID: <1305575438.19725.8.camel@lade.trondhjem.org> (raw)
In-Reply-To: <FB972601-FDA2-4C1D-B695-5D268CD568C1@oracle.com>
On Mon, 2011-05-16 at 15:40 -0400, Chuck Lever wrote:
> Hi-
>
> In minor version 1, the "lease moved" condition is indicated via a flag set in the result of a SEQUENCE operation; in mv0, it was a real NFS4ERR status code.
>
> I don't see anything in RFC 5661 that says SEQUENCE returns anything but NFS4_OK if one or more of these flags are set. But nfs41_sequence_call_done checks these status flags only when task->tk_status < 0.
>
> If SEQUENCE returns a non-NFS4_OK status code when these flags are set, and MUST be the first operation in a compound, how can anything else in any compound with a SEQUENCE operation get done?
>
> To clear a "lease moved" condition requires that the client send an operation that will get an NFS4ERR_MOVED result. I assume such a compound would require an initial SEQUENCE operation... but that should fail, since there is a "lease moved" condition.
>
> What am I missing?
>
What am _I_ missing? As far as I can see, the status flags are checked
in 2 places:
* nfs41_sequence_done() if and only if the sequence operation
status is zero (in which case we schedule a lease verification)
* In nfs4_proc_sequence(), if and only if the task->tk_status ==
0.
I can't see any checks in nfs41_sequence_call_done...
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
prev parent reply other threads:[~2011-05-16 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 19:40 SEQ4_STATUS_ question Chuck Lever
2011-05-16 19:50 ` Trond Myklebust [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1305575438.19725.8.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).