From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrew W Elble <aweits@rit.edu>
Cc: linux-nfs@vger.kernel.org, tibbs@math.uh.edu
Subject: Re: [PATCH v3 0/3] Deal with lost delegations and EKEYEXPIRED
Date: Wed, 15 Jun 2016 16:55:42 -0400 [thread overview]
Message-ID: <20160615205542.GG3848@fieldses.org> (raw)
In-Reply-To: <m2d1niw6pl.fsf@discipline.rit.edu>
On Wed, Jun 15, 2016 at 04:13:58PM -0400, Andrew W Elble wrote:
>
> > (Also: remind me what they symptoms ("lost delegation problems")
> > actually were from the point of view of users? Does the client end up
> > resending failing DELEGRETURNS and failing to make progress?)
>
> Client endlessly loops in state recovery with no path to recovery.
> I'm guessing Jason is seeing some of this as well.
OK. Just added a note at the end of the changelog saying "Without this,
Linux clients with credentials that expired while holding
delegations were getting stuck in an endless loop."--in hopes that might
help somebody recognize their problem.
--b.
next prev parent reply other threads:[~2016-06-15 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 16:52 [PATCH v3 0/3] Deal with lost delegations and EKEYEXPIRED Andrew Elble
2016-06-15 16:52 ` [PATCH v3 1/3] nfs/nfsd: Move useful bitfield ops to a commonly accessible place Andrew Elble
2016-06-15 16:52 ` [PATCH v3 2/3] nfsd: allow mach_creds_match to be used more broadly Andrew Elble
2016-06-15 16:52 ` [PATCH v3 3/3] nfsd: implement machine credential support for some operations Andrew Elble
2016-06-15 19:21 ` [PATCH v3 0/3] Deal with lost delegations and EKEYEXPIRED J. Bruce Fields
2016-06-15 19:24 ` J. Bruce Fields
2016-06-15 20:13 ` Andrew W Elble
2016-06-15 20:55 ` J. Bruce Fields [this message]
2016-06-15 19:36 ` Andrew W Elble
2016-06-15 20:55 ` J. Bruce Fields
2016-06-16 11:49 ` Jeff Layton
2016-06-16 13:27 ` 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=20160615205542.GG3848@fieldses.org \
--to=bfields@fieldses.org \
--cc=aweits@rit.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=tibbs@math.uh.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.