Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 2/2] NFS: Fall back to AUTH_SYS for SETCLIENTID (take 2)
Date: Wed, 15 May 2013 15:52:45 -0400	[thread overview]
Message-ID: <20130515195245.GC25994@fieldses.org> (raw)
In-Reply-To: <0B08EFEB-D651-4A68-8F1F-2078F62B6A5A@oracle.com>

On Wed, May 15, 2013 at 03:28:27PM -0400, Chuck Lever wrote:
> 
> On May 15, 2013, at 1:48 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> 
> > On Wed, May 15, 2013 at 01:42:58PM -0400, Chuck Lever wrote:
> >> 
> >> On May 15, 2013, at 1:39 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:
> >> 
> >>> By the way, have you looked at SP4_MACH_CRED at all yet?  It's a
> >>> selfish question (I could use something to test against), but I
> >>> think it's also what you want if you want krb5i-protected 4.1 state.
> >> 
> >> I asked about that recently and was told SP4_MACH_CRED was going the
> >> way of the do do
> > 
> > Do you remember who said that?  Is the discussion on line somewhere?
> 
> No, I mis-remembered.  I was thinking of SP4_SSV.
> 
> > 
> >> (or did I misunderstand the response from the floor?).
> >> 
> >> I'm certainly open to exploring other solutions, but I do want to be
> >> practical about it.  Will it be supported on other servers besides
> >> Linux?  Does SP4_MACH_CRED help for NFSv4.0?
> > 
> > I haven't tested other servers.  It's a 4.1-only feature.
> 
> SP4_MACH_CRED for 4.1 appears useful, but I think we would need to consider:
> 
>   o  whether SP4_MACH_CRED is a broadly implemented feature where Linux
>      clients can rely on it being there in typical environments

I'm assuming it's mandatory for servers to implement.  If there is any
example of a released server not implementing SP4_MACH_CRED, I'd like to
know.

>   o  how to address the "no keytab" issue for NFSv4.0, which does not
>      have SP4_MACH_CRED (that I am aware of)
> 
> Andy is probably more interested in seeing SP4_MACH_CRED implemented in the Linux client, as it is one solution for the "user cred expired while there is still dirty data in the client's page cache" problem, I think.

OK.

The ability to perform writes using the machine credential is built on
top of SP4_MACH_CRED, but is optional for servers to support.

--b.

  reply	other threads:[~2013-05-15 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 16:25 [PATCH 0/2] [RFC] Maybe avoid gssd upcall timeout Chuck Lever
2013-05-13 16:25 ` [PATCH 1/2] NFS: Revert commit 4edaa308 and follow-on fixes Chuck Lever
2013-05-13 16:25 ` [PATCH 2/2] NFS: Fall back to AUTH_SYS for SETCLIENTID (take 2) Chuck Lever
2013-05-15 16:04   ` J. Bruce Fields
2013-05-15 16:23     ` Chuck Lever
2013-05-15 17:16       ` J. Bruce Fields
2013-05-15 17:39         ` J. Bruce Fields
2013-05-15 17:42           ` Chuck Lever
2013-05-15 17:48             ` J. Bruce Fields
2013-05-15 19:28               ` Chuck Lever
2013-05-15 19:52                 ` J. Bruce Fields [this message]
2013-05-15 19:55                   ` Myklebust, Trond
2013-05-15 16:18 ` [PATCH 0/2] [RFC] Maybe avoid gssd upcall timeout Myklebust, Trond
2013-05-15 16:22   ` Chuck Lever
2013-05-15 16:24     ` Myklebust, Trond
2013-05-15 16:30       ` Chuck Lever
2013-05-15 16:40         ` Myklebust, Trond
2013-05-15 16:47           ` Chuck Lever
2013-05-15 18:15   ` 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=20130515195245.GC25994@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=chuck.lever@oracle.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