linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] mountd: disabling turning off TCP listeners (v2)
Date: Thu, 24 Oct 2013 14:45:07 -0400	[thread overview]
Message-ID: <20131024144507.72aa34a8@tlielax.poochiereds.net> (raw)
In-Reply-To: <1382638633-6710-1-git-send-email-steved@redhat.com>

On Thu, 24 Oct 2013 14:17:10 -0400
Steve Dickson <steved@redhat.com> wrote:

> [ Here is the second try for these patches incorporating the code review..]
> 
> Recently it was pointed out to me that the [-n | --no-tcp] flags 
> were broken in mountd. Sure enough they are and they broke 
> when nfs-utils moved to using libtirpc, which was years ago.
> 
> Obviously nobody is using these flags since has not been 
> notice until now, but it seemed to me it no longer makes 
> any sense to have flags. We really want people to use TCP 
> so why should there be a way to turn it off? It should be
> the opposite... They should be able to turn off UDP listeners
> not TCP... 
> 
> 
> Steve Dickson (3):
>   mountd: Use protocol bit fields to turn protocols off.
>   mountd: Deprecate the ability to disable TCP listeners.
>   mountd: Add the ability to disable UDP listeners.
> 
>  support/include/rpcmisc.h |  2 +-
>  support/nfs/rpcmisc.c     | 19 ++++++++++++++-----
>  support/nfs/svc_create.c  |  5 +++++
>  utils/mountd/mountd.c     | 17 ++++++++++++-----
>  utils/mountd/mountd.man   |  6 +++---
>  5 files changed, 35 insertions(+), 14 deletions(-)
> 

Sorry I'm coming in late on this...

I don't think we want to remove the ability to disable TCP listeners.

Why, you ask? We've been on a multi-year effort to move people to
NFSv4, and with that, there's no reason to have mountd listen on the
network at all.

So personally, I think it would make sense to:

a) allow people to disable listening on UDP in addition to TCP

...or...

b) add an option that prevents it from listening on any sockets for a
   v4-only configuration

In addition, we generally do want people to use UDP for the MNT
protocol because it's less apt to cause issues with reserved port
exhaustion. Given that it'll continue to listen on a UDP socket by
default, that last point is less of an issue, but that might be a good
reason to rethink this whole plan.

-- 
Jeff Layton <jlayton@redhat.com>

  parent reply	other threads:[~2013-10-24 18:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24 18:17 [PATCH 0/3] mountd: disabling turning off TCP listeners (v2) Steve Dickson
2013-10-24 18:17 ` [PATCH 1/3] mountd: Use protocol bit fields to turn protocols off Steve Dickson
2013-10-24 18:17 ` [PATCH 2/3] mountd: Deprecate the ability to disable TCP listeners Steve Dickson
2013-10-24 18:17 ` [PATCH 3/3] mountd: Add the ability to disable UDP listeners Steve Dickson
2013-10-24 18:45 ` Jeff Layton [this message]
2013-10-24 19:45   ` [PATCH 0/3] mountd: disabling turning off TCP listeners (v2) Steve Dickson
2013-10-25 11:43     ` Jeff Layton
2013-10-25 12:23       ` Steve Dickson
2013-10-25 12:29         ` Jeff Layton
2013-10-25 12:55           ` Steve Dickson
2013-10-25 13:03             ` Jeff Layton
2013-10-25 13:31               ` Steve Dickson
2013-10-25 14:20         ` J. Bruce Fields
2013-10-25 15:18           ` Steve Dickson
2013-10-26 18:55             ` J. Bruce Fields
2013-10-26 19:10               ` Stanislav Kinsbursky
2013-10-26 19:22                 ` J. Bruce Fields
2013-10-25 14:31 ` Chuck Lever

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=20131024144507.72aa34a8@tlielax.poochiereds.net \
    --to=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).