Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Jeff Layton <jlayton@redhat.com>,
	linux-nfs@vger.kernel.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 14:59:35 -0400	[thread overview]
Message-ID: <4C7D5117.6050407@RedHat.com> (raw)
In-Reply-To: <20100831180745.GA11361@fieldses.org>



On 08/31/2010 02:07 PM, J. Bruce Fields wrote:
> On Tue, Aug 31, 2010 at 01:18:46PM -0400, Steve Dickson wrote:
>> I really don't think we need to rip the guts out of 
>> mountd and exportfs just to remove this one nfsctl() in rpc.nfsd.
> 
> I agree.
> 
>>> Dropping backwards compatibility may be a reasonable thing to do, but
>>> it's something that we should be very clear about, and that we should
>>> put in a patch that does that and nothing else.
>> So you are talking about doing a complete rewrite of mountd and exportfs
>> just to take out that one call from rpc.nfsd... I just don't see the
>> justification... If we are going to do that, let just think about rewriting
>> all the tools to make the more v4 friendly... something we talked about
>> at the last bakeathon...
> 
> All I'm asking is that any patch which disables support for older
> kernels (by ceasing to do the nfsctl) be a *separate* patch that clearly
> states which kernels we're dropping support for.
Fine. The taking out the nfsclt() and/or the adding of the error check
on the mount (basically causing nfsclt() to never be called) will be in 
a separate clearly documented patch.....

> 
> Once we decide to drop such support (if we do), that might allow us to
> rip out a lot of additional code.  That can be done later.
I agree... 

steved.

  reply	other threads:[~2010-08-31 18:59 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
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 [this message]
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=4C7D5117.6050407@RedHat.com \
    --to=steved@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.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