From: Jeff Layton <jlayton@redhat.com>
To: "J. Bruce Fields" <bfields@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [0/2] make nfsd's setclientid behavior migration-friendly
Date: Thu, 22 Sep 2016 07:07:03 -0400 [thread overview]
Message-ID: <1474542423.1706.4.camel@redhat.com> (raw)
In-Reply-To: <1474481025-23702-1-git-send-email-bfields@redhat.com>
On Wed, 2016-09-21 at 14:03 -0400, J. Bruce Fields wrote:
> Clients mounting multiple servers with the "migration" option may find
> some mounts are made from the incorrect server.
>
> I think this is really a bug in RFC 7931, and that RFC and the client
> need fixing, but this is easy to mitigate on the server. I'll make an
> attempt at a client patch too.
>
> --b.
>
>
Both look reasonable to me:
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2016-09-22 11:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 18:03 [0/2] make nfsd's setclientid behavior migration-friendly J. Bruce Fields
2016-09-21 18:03 ` [PATCH 1/2] nfsd: randomize SETCLIENTID reply to help distinguish servers J. Bruce Fields
2016-09-21 18:03 ` [PATCH 2/2] nfsd4: setclientid_confirm with unmatched verifier should fail J. Bruce Fields
2016-09-22 11:07 ` Jeff Layton [this message]
2016-09-22 14:46 ` [0/2] make nfsd's setclientid behavior migration-friendly J. Bruce Fields
2016-09-22 15:36 ` Jeff Layton
2016-09-22 20:23 ` J. Bruce Fields
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=1474542423.1706.4.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@redhat.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).