All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Neil Brown <neilb@suse.de>,
	linux-nfs@vger.kernel.org, chuck.lever@oracle.com,
	steved@redhat.com
Subject: Re: [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet
Date: Sun, 29 Aug 2010 15:31:02 -0400	[thread overview]
Message-ID: <20100829193102.GA1627@fieldses.org> (raw)
In-Reply-To: <20100828222450.7ca62e49@corrin.poochiereds.net>

On Sat, Aug 28, 2010 at 10:24:50PM -0400, Jeff Layton wrote:
> I considered that when I did this, but didn't know if we could count on
> nfsdfs automatically being mounted up when nfsd.ko is plugged in. I
> went with calling system() since I figured we'd be making less
> assumptions about modprobe.conf configuration.
> 
> FWIW, at least on fedora the /bin/mount here usually returns an
> error. /bin/mount calls mount() and that triggers a request_module()
> for nfsdfs. That triggers modprobe to mount the fs, and /bin/mount then
> returns an error since it's already mounted. The error though is
> harmless in this case since the fs gets mounted up anyway.
> 
> If the consensus is that using a no-op nfsctl() call is better than
> shelling out to /bin/mount here, then I'll go with that. It seems
> though like the patch I've already proposed would allow for nfsdfs to
> end up mounted even when modprobe.conf isn't set up to do it.

I'd rather not rely on modprobe.  It's partly a personal grudge: I
usually build nfsd into kernels when I test, and that always requires
a minor scuffle or two with init scripts that assume nfsd should be a
module.

--b.

  reply	other threads:[~2010-08-29 19:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 11:35 [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet Jeff Layton
2010-08-28 22:29 ` Neil Brown
2010-08-28 22:38 ` Neil Brown
2010-08-29  2:24   ` Jeff Layton
2010-08-29 19:31     ` J. Bruce Fields [this message]
2010-08-29 19:37     ` J. Bruce Fields
2010-08-29 22:12       ` Neil Brown
2010-08-30 15:51 ` Steve Dickson
2010-08-30 16:16   ` Jeff Layton
2010-08-30 16:53     ` Steve Dickson
2010-08-30 17:04       ` J. Bruce Fields
2010-08-30 17:22         ` Jeff Layton
2010-08-31 12:14         ` Steve Dickson
2010-08-30 17:48       ` Jeff Layton
2010-08-31 12:24         ` Steve Dickson
2010-08-31 12:43           ` Jeff Layton
2010-08-31 14:49             ` Steve Dickson
2010-08-31 15:10               ` Jeff Layton
2010-08-31 15:13                 ` J. Bruce Fields
2010-08-31 15:18                   ` Steve Dickson
2010-08-31 15:51                     ` J. Bruce Fields
2010-08-31 16:13                       ` Steve Dickson
2010-08-31 16:15                         ` J. Bruce Fields
2010-08-31 17:18                           ` Steve Dickson
2010-08-31 18:07                             ` J. Bruce Fields
2010-08-31 18:59                               ` Steve Dickson
2010-08-31 19:02                                 ` Jeff Layton

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