From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v1] nfs: Don't increment lock sequence ID after NFS4ERR_MOVED
Date: Mon, 23 Jan 2017 11:49:13 -0500 [thread overview]
Message-ID: <20170123164913.GB9493@fieldses.org> (raw)
In-Reply-To: <69D3212A-874D-42A2-BE65-F3A01B061A87@oracle.com>
On Mon, Jan 23, 2017 at 10:01:27AM -0500, Chuck Lever wrote:
>
> > On Jan 22, 2017, at 2:04 PM, Chuck Lever <chuck.lever@oracle.com> wrote:
> >
> > Xuan Qi reports that the Linux NFSv4 client failed to lock a file
> > that was migrated. The steps he observed on the wire:
> >
> > 1. The client sent a LOCK request
> > 2. The server replied NFS4ERR_MOVED
> > 3. The client switched to the destination server
> > 4. The client sent the LOCK request again with a bumped
> > lock sequence ID
> > 5. The server rejected the LOCK request with NFS4ERR_BAD_SEQID
>
> The list of steps could be more clear:
>
> 1. The client sent a LOCK request to the source server
> 2. The source server replied NFS4ERR_MOVED
> 3. The client switched to the destination server
> 4. The client sent the same LOCK request to the destination
> server with a bumped lock sequence ID
> 5. The destination server rejected the LOCK request with
> NFS4ERR_BAD_SEQID
>
>
> > RFC 3530 section 8.1.5 provides a list of NFS errors which do not
> > bump a lock sequence ID.
> >
> > However, RFC 3530 is now obsoleted by RFC 7530. In RFC 7530 section
> > 9.1.7, this list has been updated by the addition of NFS4ERR_MOVED.
I guess we figured the backwards-incompatible change was OK since
essentially the Solaris server is the first we know of to be making real
use of NFS4ERR_MOVED?
And probably it's required for the their implementation because the old
server no longer has the ability to update the state once it's reached
the point of returning ERR_MOVED.
OK, makes sense to me, I think.
--b.
> >
> > Reported-by: Xuan Qi <xuan.qi@oracle.com>
> > Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> > Cc: stable@vger.kernel.org # v3.7+
> > ---
> > include/linux/nfs4.h | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/include/linux/nfs4.h b/include/linux/nfs4.h
> > index bca5363..1b1ca04 100644
> > --- a/include/linux/nfs4.h
> > +++ b/include/linux/nfs4.h
> > @@ -282,7 +282,7 @@ enum nfsstat4 {
> >
> > static inline bool seqid_mutating_err(u32 err)
> > {
> > - /* rfc 3530 section 8.1.5: */
> > + /* See RFC 7530, section 9.1.7 */
> > switch (err) {
> > case NFS4ERR_STALE_CLIENTID:
> > case NFS4ERR_STALE_STATEID:
> > @@ -291,6 +291,7 @@ static inline bool seqid_mutating_err(u32 err)
> > case NFS4ERR_BADXDR:
> > case NFS4ERR_RESOURCE:
> > case NFS4ERR_NOFILEHANDLE:
> > + case NFS4ERR_MOVED:
> > return false;
> > };
> > return true;
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> Chuck Lever
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-01-23 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 19:04 [PATCH v1] nfs: Don't increment lock sequence ID after NFS4ERR_MOVED Chuck Lever
2017-01-23 15:01 ` Chuck Lever
2017-01-23 16:49 ` J. Bruce Fields [this message]
2017-01-24 19:06 ` Chuck Lever
2017-01-24 19:15 ` J. Bruce Fields
2017-01-24 19:31 ` Chuck Lever
2017-01-24 19:41 ` J. Bruce Fields
2017-01-24 19:53 ` J. Bruce Fields
2017-01-24 19:58 ` Chuck Lever
2017-01-24 19:54 ` Chuck Lever
2017-01-24 20:23 ` Trond Myklebust
2017-01-24 20:31 ` bfields
2017-01-25 19:58 ` Chuck Lever
2017-01-25 20:08 ` Chuck Lever
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=20170123164913.GB9493@fieldses.org \
--to=bfields@fieldses.org \
--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