linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andrew Elble <aweits@rit.edu>
Cc: linux-nfs@vger.kernel.org, dros@primarydata.com
Subject: Re: [PATCH v2 0/3] Deal with lost delegations and EKEYEXPIRED
Date: Wed, 20 Jan 2016 17:34:29 -0500	[thread overview]
Message-ID: <20160120223429.GA26860@fieldses.org> (raw)
In-Reply-To: <1453147702-42961-1-git-send-email-aweits@rit.edu>

On Mon, Jan 18, 2016 at 03:08:19PM -0500, Andrew Elble wrote:
> I've finally discovered that the majority of our lost delegation problems
> come from EKEYEXPIRED.

These patches only seem to change behavior in WRONGSEC cases.  Could you
explain what these patches have to do with the lost delegation and
EKEYEXPIRED problems?

--b.

> This seems to work fine in our environment, but
> I am unsure of the ramifications of this in a broader context, so it's
> time to get other folks to look at it.
> 
> v2: fix kbuild robot err on CONFIG_NFSD_V4 unset
>     kerneldoc header on nfsd4_spo_must_allow
>     removed LAYOUTRETURN as I currently can't test it
> 
> 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        |  4 +++
>  fs/nfsd/nfs4proc.c      | 69 +++++++++++++++++++++++++++++++++++++++++++++++++
>  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, 143 insertions(+), 46 deletions(-)
> 
> -- 
> 2.6.3

  parent reply	other threads:[~2016-01-20 22:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 20:08 [PATCH v2 0/3] Deal with lost delegations and EKEYEXPIRED Andrew Elble
2016-01-18 20:08 ` [PATCH v2 1/3] nfs/nfsd: Move useful bitfield ops to a commonly accessible place Andrew Elble
2016-01-18 20:08 ` [PATCH v2 2/3] nfsd: allow mach_creds_match to be used more broadly Andrew Elble
2016-01-18 20:08 ` [PATCH v2 3/3] nfsd: implement machine credential support for some operations Andrew Elble
2016-01-20 22:53   ` J. Bruce Fields
2016-01-21 16:07     ` J. Bruce Fields
2016-01-21 19:01   ` J. Bruce Fields
2016-01-21 19:30     ` Andrew W Elble
2016-01-21 19:50       ` J. Bruce Fields
2016-01-22  0:01         ` Andrew W Elble
2016-01-22 15:24           ` J. Bruce Fields
2016-01-22 16:06             ` Trond Myklebust
2016-01-22 15:40   ` J. Bruce Fields
2016-01-22 16:09     ` Andrew W Elble
2016-01-22 16:36       ` J. Bruce Fields
2016-01-20 22:34 ` J. Bruce Fields [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-01-05 18:55 [PATCH v2 0/3] Deal with lost delegations and EKEYEXPIRED Andrew Elble

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=20160120223429.GA26860@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aweits@rit.edu \
    --cc=dros@primarydata.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).