From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
Zdenek Salvet <salvet@ics.muni.cz>,
Lukas Hejtmanek <xhejtman@ics.muni.cz>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 backchannel authentication
Date: Fri, 10 Aug 2012 13:23:22 -0400 [thread overview]
Message-ID: <20120810172322.GA17404@fieldses.org> (raw)
In-Reply-To: <20120810152039.21eaa5a6@notabene.brown>
On Fri, Aug 10, 2012 at 03:20:39PM +1000, NeilBrown wrote:
> On Thu, 9 Aug 2012 15:53:01 +0000 "Myklebust, Trond"
> <Trond.Myklebust@netapp.com> wrote:
>
> > On Thu, 2012-08-09 at 10:45 -0400, J. Bruce Fields wrote:
> > > On Thu, Aug 09, 2012 at 10:06:42AM +0200, Zdenek Salvet wrote:
> > > > On Wed, Aug 08, 2012 at 01:18:09PM +0000, Myklebust, Trond wrote:
> > > > > > We don't see any hard failures because NFS protocol does
> > > > > > not depend on working callback RPCs, but no delegations are granted
> > > > > > (we had nfs-kernel-server package installed on clients before which masked
> > > > > > the bug).
> > > > >
> > > > > So your gripe that you object to us requiring you to run rpc.svcgssd in
> > > > > order to obtain server features such as NFSv4 callbacks?
> > > >
> > > > Absolutely not! Just thinking why we did not notice the problem earlier ...
> > >
> > > I wonder if there's anything we could do to make this more automatic,
> > > though: e.g., perhaps whichever scripts are launching one of the gss
> > > daemons should be replaced by one that launches both, since that's
> > > generally what you'll want for NFSv4.0. (Not necessary for other
> > > versions, but it doesn't hurt much.)
> > >
> > > Or perhaps they could be started on demand somehow.
> >
> > How is this any different to requiring that the user start rpc.statd
> > before launching an NFSv3 mount? Just document the requirement if it
> > isn't already clear enough, and we can move on.
>
> 'mount.nfs' checks if statd is running and will start it if it isn't ....
> which will probably annoy systemd as it likes to keep daemons in their own
> little box. I guess systemd can be configured to register as statd and
> auto-start it on the first 'are you there' request.
>
> Could the same thing be done with rpc.svcgssd? Get it to auto-start either
> by mount.nfs checking and running something, or by systemd pre-registering
> the RPC port or something?
I wonder how hard it would be to teach systemd to do the
socket-activation trick with the cache upcalls: so, open the channel
file, wait till its readable, then kick off svcgssd and hand off the
file descriptor to it.
--b.
prev parent reply other threads:[~2012-08-10 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 13:55 NFSv4 backchannel authentication Lukas Hejtmanek
2012-08-07 15:41 ` J. Bruce Fields
2012-08-07 15:59 ` Myklebust, Trond
2012-08-07 16:12 ` Lukas Hejtmanek
2012-08-08 7:58 ` Zdenek Salvet
2012-08-08 13:18 ` Myklebust, Trond
2012-08-09 8:06 ` Zdenek Salvet
2012-08-09 14:45 ` J. Bruce Fields
2012-08-09 15:53 ` Myklebust, Trond
2012-08-09 16:28 ` Lukas Hejtmanek
2012-08-09 16:30 ` Myklebust, Trond
2012-08-09 16:38 ` J. Bruce Fields
2012-08-09 16:49 ` Myklebust, Trond
2012-08-09 16:50 ` J. Bruce Fields
2012-08-09 17:58 ` Zdenek Salvet
2012-08-09 18:01 ` [PATCH] README: note gssd/svcgssd may be needed on both sides J. Bruce Fields
2012-08-10 5:20 ` NFSv4 backchannel authentication NeilBrown
2012-08-10 17:23 ` J. Bruce Fields [this message]
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=20120810172322.GA17404@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=salvet@ics.muni.cz \
--cc=xhejtman@ics.muni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.