All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
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: Mon, 30 Aug 2010 13:04:12 -0400	[thread overview]
Message-ID: <20100830170412.GC9316@fieldses.org> (raw)
In-Reply-To: <4C7BE1FC.2020400@RedHat.com>

On Mon, Aug 30, 2010 at 12:53:16PM -0400, Steve Dickson wrote:
> On 08/30/2010 12:16 PM, Jeff Layton wrote:
> > How this as an alternate proposal?
> > 
> > We attempt to mount up nfsdfs. If the "threads" file still isn't
> > present after the attempt, we then log a warning and go with the
> > nfsctl() interface?
> Has anybody test this legacy interface lately?? Does anybody anybody
> depend on the existence of this interface??? I would guess the answer
> would be no to both questions... So I see this as an opportunity so
> simplify the code... which is always a good thing... 
> 
> So I would have no problem saying from the next release of nfs-utils,
> the legacy interface is no longer supported... especially if there are
> issues with IPV6.

In general I'd like backwards-compatibility to be a very high priority,
in both directions.  (Both continuing to support old nfs-utils in new
kernels, and supporting old kernels with new nfs-utils.)  Among other
advantages, it makes it easier to troubleshoot user problems if we don't
have to ask them to upgrade multiple packages at once to test a fix.

On the other hand, the nfsctl interface is pretty old (when did the new
stuff go in, exactly?).

On the other other hand, Jeff's patch isn't really very complicated.
(Though the amount of additional code we could delete might be large.)

--b.

  reply	other threads:[~2010-08-30 17:04 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 [this message]
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=20100830170412.GC9316@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 \
    /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.