From: Jeff Layton <jlayton@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: linux-nfs@vger.kernel.org, bfields@fieldses.org, chuck.lever@oracle.com
Subject: Re: [PATCH] rpc.nfsd: mount up nfsdfs is it doesn't appear to be mounted yet
Date: Tue, 31 Aug 2010 11:10:08 -0400 [thread overview]
Message-ID: <20100831111008.157618f4@corrin.poochiereds.net> (raw)
In-Reply-To: <4C7D1694.6000708@RedHat.com>
On Tue, 31 Aug 2010 10:49:56 -0400
Steve Dickson <SteveD@redhat.com> wrote:
> >
> > To keep this on track, I think we need to treat this as 2 separate
> > discussions:
> >
> > 1) how to we ensure that /proc/fs/nfsd is actually mounted when
> > rpc.nfsd is run?
> >
> > 2) what do we do about the legacy nfsctl() interface?
> >
> > These are separate but related questions...
I was just pointing out that checking the return code from the system()
call isn't sufficient. Because of the way most people have modprobe set
up, it can return an error even though nfsdfs ended up being mounted
anyway. Checking for the presence of the file after attempting the
mount would be a more reliable test.
Assuming we're in agreement there, we have another question to
settle...If the mount attempt fails, what should we do about it?
With my original patch, we fall back to using nfsctl(). You're
suggesting that we should error out there. I'm not opposed to that, but
it does mean dropping support for some really old kernels. It also
means that we can remove some dead code in rpc.nfsd.
OTOH, the fallback might allow nfsd to keep working for some people.
Maybe it would be better to just log a scary warning and fall back to
using nfsctl() for now.
In a couple of releases, we could start returning an error there and
rip out the legacy interface code, or compile it out by default and
allow people to compile it in via a configure option?
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2010-08-31 15:06 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
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 [this message]
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=20100831111008.157618f4@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=SteveD@redhat.com \
--cc=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