netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: netdev@vger.kernel.org, Linux kernel <linux-kernel@vger.kernel.org>
Subject: sunrpc port allocation and IANA reserved list
Date: Tue, 10 Nov 2009 11:43:23 -0600	[thread overview]
Message-ID: <4AF9A63B.6010101@nortel.com> (raw)


By default sunrpc ports are allocated at random in the range 665-1023U.
 However, there are many ports within this range which have been
reserved by the IANA (and others like port 921 which are not formally
reserved but are "well-known").

Given that a userspace application can be stopped and restarted at any
time, and a sunrpc registration can happen at any time, what is the
expected mechanism to prevent the kernel from allocating a port for use
by sunrpc that reserved or well-known?

Apparently Redhat and Debian have distro-specific ways of dealing with
this, but is there a standard solution?  Should there be?

The current setup seems suboptimal.

Chris

             reply	other threads:[~2009-11-10 17:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 17:43 Chris Friesen [this message]
2009-11-10 17:53 ` sunrpc port allocation and IANA reserved list Ben Hutchings
2009-11-10 18:37   ` Chris Friesen
2009-11-10 18:48     ` Chris Friesen
2009-11-10 20:26     ` Trond Myklebust
2009-11-10 21:06       ` Chris Friesen
2009-11-10 21:17         ` Trond Myklebust
2009-11-10 21:58           ` Trond Myklebust
2009-11-10 21:32         ` Ben Hutchings
2009-11-10 21:34           ` Chuck Lever
2009-11-10 21:42             ` Ben Hutchings
2009-11-10 21:54           ` Chris Friesen
2009-11-10 22:14           ` Trond Myklebust

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=4AF9A63B.6010101@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).