All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Neil Brown <neilb@suse.de>,
	linux-nfs@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [PATCH] nfsd: select CONFIG_PROC_FS in nfsv4 and gss	server cases
Date: Thu, 15 Nov 2007 17:20:02 -0500	[thread overview]
Message-ID: <20071115222002.GG7128@fieldses.org> (raw)
In-Reply-To: <1195164396.8905.62.camel@heimdal.trondhjem.org>

On Thu, Nov 15, 2007 at 05:06:36PM -0500, Trond Myklebust wrote:
> 
> On Thu, 2007-11-15 at 16:57 -0500, J. Bruce Fields wrote:
> > The server depends on upcalls under /proc to support nfsv4 and gss.
> > 
> > Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> > ---
> >  fs/Kconfig |    2 ++
> >  1 files changed, 2 insertions(+), 0 deletions(-)
> > 
> > diff --git a/fs/Kconfig b/fs/Kconfig
> > index 429a002..340b233 100644
> > --- a/fs/Kconfig
> > +++ b/fs/Kconfig
> > @@ -1670,6 +1670,8 @@ config NFSD
> >  	select CRYPTO_MD5 if NFSD_V4
> >  	select CRYPTO if NFSD_V4
> >  	select FS_POSIX_ACL if NFSD_V4
> > +	select PROC_FS if NFSD_V4
> > +	select PROC_FS if SUNRPC_GSS
> >  	help
> >  	  If you want your Linux box to act as an NFS *server*, so that other
> >  	  computers on your local network which support NFS can access certain
> 
> What if you just want it to act as a client? No need for PROC_FS then...

We're inside the config NFSD clause, so if you really want *just* a
client, then this doesn't change anything.

So the problematic case would be if you want it to be both client and
server, and want to use GSS on the client, but don't want to use GSS on
the server, and don't want to compile in proc.

Is that an important case?

If so, OK, we can remove the "select PROC_FS if SUNRPC_GSS".  But it
might help to at least keep some documentation here though so people
know they need proc if they expect GSS to work on the server.

I suppose we could just add another "server-side gss support" config
entry whose only reason for existance is to turn on PROC_FS.

--b.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-11-15 22:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 21:56 8 patches cleaning up nfsd initialization J. Bruce Fields
2007-11-15 21:56 ` [PATCH] knfsd: cleanup nfsd4 properly on module init failure J. Bruce Fields
2007-11-15 21:56   ` [PATCH] nfsd: cleanup nfsd module initialization cleanup J. Bruce Fields
2007-11-15 21:56     ` [PATCH] nfsd: fail module init on reply cache init failure J. Bruce Fields
2007-11-15 21:56       ` [PATCH] knfsd: cache unregistration needn't return error J. Bruce Fields
2007-11-15 21:57         ` [PATCH] nfsd: select CONFIG_PROC_FS in nfsv4 and gss server cases J. Bruce Fields
2007-11-15 21:57           ` [PATCH] nfsd: fail init on /proc/fs/nfs/exports creation failure J. Bruce Fields
2007-11-15 21:57             ` [PATCH] nfsd: move cache proc (un)registration to separate function J. Bruce Fields
2007-11-15 21:57               ` [PATCH] knfsd: allow cache_register to return error on failure J. Bruce Fields
2007-11-15 22:06           ` [PATCH] nfsd: select CONFIG_PROC_FS in nfsv4 and gss server cases Trond Myklebust
2007-11-15 22:20             ` J. Bruce Fields [this message]
2007-11-15 22:25               ` Trond Myklebust
2007-11-15 22:26                 ` J. Bruce Fields
2007-11-16 14:29       ` [PATCH] nfsd: fail module init on reply cache init failure Peter Staubach
2007-11-16 15:30         ` J. Bruce Fields
2007-11-16 15:38           ` Peter Staubach
2007-11-16 16:01             ` J. Bruce Fields
2007-11-16 16:22               ` Peter Staubach
2007-11-16 16:27                 ` J. Bruce Fields
2007-11-16  0:41 ` 8 patches cleaning up nfsd initialization Neil Brown
2007-11-16  3:19   ` 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=20071115222002.GG7128@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.