From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrew Elble <aweits@rit.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Deal with lost delegations and EKEYEXPIRED
Date: Wed, 15 Jun 2016 15:24:15 -0400 [thread overview]
Message-ID: <20160615192415.GB3848@fieldses.org> (raw)
In-Reply-To: <20160615192116.GA3848@fieldses.org>
On Wed, Jun 15, 2016 at 03:21:16PM -0400, J. Bruce Fields wrote:
> Looks good, thanks.
>
> On Wed, Jun 15, 2016 at 12:52:06PM -0400, Andrew Elble wrote:
> > The majority of our lost delegation problems come from the inability
> > to return the delegations when the credentials that obtained them
> > have expired (conundrum mentioned in RFC 5661 18.35.3)
>
> I take it you've tested these and verified delegations aren't getting
> lost? Are there client changes needed as well, or is the client already
> doing the right thing?
(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?)
--b.
>
> --b.
>
> >
> > ObMemoryJog:
> >
> > http://www.spinics.net/lists/linux-nfs/msg56230.html
> >
> > v3: removal of OP_IS_PUTFH_LIKE checks
> > added clarification of addressing the conundrum
> >
> > Andrew Elble (3):
> > nfs/nfsd: Move useful bitfield ops to a commonly accessible place
> > nfsd: allow mach_creds_match to be used more broadly
> > nfsd: implement machine credential support for some operations
> >
> > fs/nfsd/export.c | 10 ++++++++++
> > fs/nfsd/nfs4proc.c | 39 +++++++++++++++++++++++++++++++++++++
> > fs/nfsd/nfs4state.c | 32 ++++++++++++++++++++++++-------
> > fs/nfsd/nfs4xdr.c | 51 ++++++++++++++++++++++---------------------------
> > fs/nfsd/nfsd.h | 5 +++++
> > fs/nfsd/state.h | 1 +
> > fs/nfsd/xdr4.h | 5 +++++
> > include/linux/nfs4.h | 11 +++++++++++
> > include/linux/nfs_xdr.h | 11 -----------
> > 9 files changed, 119 insertions(+), 46 deletions(-)
> >
> > --
> > 2.6.3
next prev parent reply other threads:[~2016-06-15 19:24 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 [this message]
2016-06-15 20:13 ` Andrew W Elble
2016-06-15 20:55 ` J. Bruce Fields
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=20160615192415.GB3848@fieldses.org \
--to=bfields@fieldses.org \
--cc=aweits@rit.edu \
--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).