From: "Chris Friesen" <cfriesen@nortel.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: sunrpc port allocation and IANA reserved list
Date: Tue, 10 Nov 2009 12:37:03 -0600 [thread overview]
Message-ID: <4AF9B2CF.6050305@nortel.com> (raw)
In-Reply-To: <1257875623.2834.19.camel@achroite.uk.solarflarecom.com>
On 11/10/2009 11:53 AM, Ben Hutchings wrote:
> On Tue, 2009-11-10 at 11:43 -0600, Chris Friesen wrote:
>> 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.
>
> I believe both RH and Debian are using the same implementation:
> <http://cyberelk.net/tim/software/portreserve/>.
That helps with the startup case, but still leaves a possible hole if an
app using a fixed port number is restarted at runtime. During the
window where nobody is bound to the port, the kernel could randomly
assign it to someone else.
Chris
next prev parent reply other threads:[~2009-11-10 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 17:43 sunrpc port allocation and IANA reserved list Chris Friesen
2009-11-10 17:53 ` Ben Hutchings
2009-11-10 18:37 ` Chris Friesen [this message]
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=4AF9B2CF.6050305@nortel.com \
--to=cfriesen@nortel.com \
--cc=bhutchings@solarflare.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).