Linux NFS development
 help / color / mirror / Atom feed
From: Weston Andros Adamson <dros@primarydata.com>
To: Andrew Elble <aweits@rit.edu>
Cc: linux-nfs list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH RFC 0/4] Deal with lost delegations and EKEYEXPIRED
Date: Tue, 8 Dec 2015 16:38:22 -0500	[thread overview]
Message-ID: <38076235-99FC-4CC7-8F16-3518A58CABA2@primarydata.com> (raw)
In-Reply-To: <1449067193-53310-1-git-send-email-aweits@rit.edu>

These patches look reasonable to me. I agree with Trond that you should
separate the client and server patches.

One part I’m not sure about is in nfsd4_spo_must_allow dealing with putfh like
ops vs not putfh-like ops. I’ll have to check the spec and take a deeper look at
that when I get some time, but maybe a brief explanation in a comment would
help?

To be honest, I've always been hazy on where in the spec the ramifications of
SP4_MACH_CRED only covering part of a compound is discussed… I’ll take a
look soon.

-dros



> On Dec 2, 2015, at 9:39 AM, Andrew Elble <aweits@rit.edu> wrote:
> 
> I've finally discovered that the majority of our lost delegation problems
> come from EKEYEXPIRED. 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.
> 
> Andrew Elble (4):
>  nfs/nfsd: Move useful bitfield ops to a commonly accessible place
>  nfs: machine credential support for additional operations
>  nfsd: allow mach_creds_match to be used more broadly
>  nfsd: implement machine credential support for some operations
> 
> fs/nfs/nfs4proc.c         | 20 +++++++++++++++++
> fs/nfsd/export.c          |  4 ++++
> fs/nfsd/nfs4proc.c        | 55 +++++++++++++++++++++++++++++++++++++++++++++++
> fs/nfsd/nfs4state.c       | 35 ++++++++++++++++++++++++------
> fs/nfsd/nfs4xdr.c         | 51 ++++++++++++++++++++-----------------------
> fs/nfsd/nfsd.h            |  1 +
> fs/nfsd/state.h           |  1 +
> fs/nfsd/xdr4.h            |  5 +++++
> include/linux/nfs4.h      | 11 ++++++++++
> include/linux/nfs_fs_sb.h |  1 +
> include/linux/nfs_xdr.h   | 11 ----------
> 11 files changed, 149 insertions(+), 46 deletions(-)
> 
> -- 
> 2.6.3
> 
> --
> 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


  parent reply	other threads:[~2015-12-08 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 14:39 [PATCH RFC 0/4] Deal with lost delegations and EKEYEXPIRED Andrew Elble
2015-12-02 14:39 ` [PATCH RFC 1/4] nfs/nfsd: Move useful bitfield ops to a commonly accessible place Andrew Elble
2015-12-02 14:39 ` [PATCH RFC 2/4] nfs: machine credential support for additional operations Andrew Elble
2015-12-06 21:47   ` Trond Myklebust
2015-12-08 18:29     ` Andrew W Elble
2015-12-02 14:39 ` [PATCH RFC 3/4] nfsd: allow mach_creds_match to be used more broadly Andrew Elble
2015-12-02 14:39 ` [PATCH RFC 4/4] nfsd: implement machine credential support for some operations Andrew Elble
2015-12-08 21:38 ` Weston Andros Adamson [this message]
2015-12-09 14:17   ` [PATCH RFC 0/4] Deal with lost delegations and EKEYEXPIRED Andrew W 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=38076235-99FC-4CC7-8F16-3518A58CABA2@primarydata.com \
    --to=dros@primarydata.com \
    --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