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 13:16:01 -0400 [thread overview]
Message-ID: <20130515171601.GL16811@fieldses.org> (raw)
In-Reply-To: <961AC5FB-617E-48FB-A35F-5E1A25213292@oracle.com>
On Wed, May 15, 2013 at 12:23:12PM -0400, Chuck Lever wrote:
>
> On May 15, 2013, at 12:04 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:
>
> > On Mon, May 13, 2013 at 12:25:28PM -0400, Chuck Lever wrote:
> >> Now that commit 4edaa308 "NFS: Use "krb5i" to establish NFSv4 state
> >> whenever possible" is reverted...
> >>
> >> NFSv4 server trunking detection was added with commit 05f4c350 "NFS:
> >> Discover NFSv4 server trunking when mounting" in v3.7. One of the
> >> issues that the reverted commit 4edaa308 tried to address was that
> >> when server trunking detection was added, we broke the ability to
> >> mount krb5 exports when the client has no keytab.
> >
> > And that happened because we started asking gssd explicitly for a
> > context for a machine principal instead of for uid=0? Or for some other
> > reason?
>
> We've asked gssd for a machine credential for SETCLIENTID for a while now, so "some other reason." I honestly don't know exactly why it stopped working with my change, but someone bisected it to that one.
>
> But we've always had some issue with the "no keytab" case because we do require a machine credential for SETCLIENTID. I'm suggesting a fix for the broad class of problems using "sec=krb5?" that arise due to a missing keytab on the client.
>
> In this case we need the fix sooner rather than later because it stopped working in 3.7.
>
> >
> >> We still need to
> >> address that regression.
> >>
> >> Let's try a narrow approach to re-enabling sec=krb5 mounts without a
> >> local system keytab, and worry about the other issues when we can
> >> plan concomitant user space and kernel changes.
> >>
> >> When a GSS security flavor is used on a mount, allow the security
> >> flavor for state management to fall back to AUTH_SYS if there is
> >> a problem setting up a GSS context for it.
> >
> > This brings back the delay in the case gssd isn't running, doesn't it?
>
> No. "When a GSS flavor is used" means ONLY when a GSS flavor is used. We make the minimal assumption that using a GSS flavor for a mount means the administrator either has gssd running or wants to know when it isn't, and can tolerate a delay in that case.
Oh, got it, thanks.--b.
next prev parent reply other threads:[~2013-05-15 17:16 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 [this message]
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
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=20130515171601.GL16811@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