All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Jeff Layton <jlayton@redhat.com>, Neil Brown <neilb@suse.de>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet (try #2)
Date: Thu, 2 Sep 2010 14:49:43 -0400	[thread overview]
Message-ID: <20100902184943.GA24608@fieldses.org> (raw)
In-Reply-To: <4C7FD3D1.30601@RedHat.com>

On Thu, Sep 02, 2010 at 12:41:53PM -0400, Steve Dickson wrote:
> 
> 
> On 09/02/2010 10:25 AM, J. Bruce Fields wrote:
> > On Thu, Sep 02, 2010 at 10:04:19AM -0400, Chuck Lever wrote:
> >> Neil's patches are now in upstream nfs-utils.  You can disable all of
> >> the network listeners with command line options on mountd.
> >>
> >> It's been said that people complain that they don't like running
> >> rpc.mountd on NFSv4-only servers.  I'm not sure why that's a problem
> >> we have to fix with a code change.  Better documentation, better
> >> automatic configuration detection in the NFS start-up scripts, or
> >> simply renaming rpc.mountd could solve this issue without the need for
> >> rip-and-replace of well-tested code.
> I think a lot of the problems come from people having to open up 
> their firewalls and such... basically security issues..  was well 
> as having "extra" daemons stealing cpu cycles... 
> 
> > 
> > Yeah, I've suggested a separate upcall-handling daemon before, but agree
> > that for now we should leave well enough alone.
> What would be the deciding factor to start this work? Maybe when
> Trond done splitting up kernel code into separate version modules? 

I think it's at most an idea to keep in the back of our minds in case it
looks useful some day--not a todo we should schedule.

--b.

  reply	other threads:[~2010-09-02 18:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 19:32 [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet (try #2) Jeff Layton
2010-09-01 20:48 ` J. Bruce Fields
2010-09-01 20:56   ` Jeff Layton
2010-09-01 21:31     ` Neil Brown
2010-09-02  0:17       ` Jeff Layton
2010-09-02  1:32       ` J. Bruce Fields
2010-09-02 11:29       ` Steve Dickson
2010-09-02 11:55         ` Jeff Layton
2010-09-02 14:04           ` Chuck Lever
2010-09-02 14:25             ` J. Bruce Fields
2010-09-02 16:41               ` Steve Dickson
2010-09-02 18:49                 ` J. Bruce Fields [this message]
2010-09-02 14:30       ` Chuck Lever
2010-09-14 13:23 ` Jeff Layton
2010-09-15 20:09   ` Steve Dickson
2010-09-15 22:31     ` Jeff Layton
2010-09-16 11:06       ` Steve Dickson
2010-09-16 11:32         ` Jeff Layton
     [not found]           ` <20100916073203.2c217bfc-xSBYVWDuneFaJnirhKH9O4GKTjYczspe@public.gmane.org>
2010-09-16 11:43             ` Steve Dickson
2010-09-16 12:30     ` Steve Dickson
2010-09-16 13:02 ` [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet (try #4) Steve Dickson
     [not found]   ` <4C921580.2050903-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2010-09-16 13:40     ` Jeff Layton
2010-09-16 21:32     ` Steve Dickson

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=20100902184943.GA24608@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.