From: Steve Dickson <SteveD@redhat.com>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net, akpm@osdl.org
Subject: Re: [PATCH] Fix xprt_bindresvport
Date: Thu, 14 Jul 2005 12:00:11 -0400 [thread overview]
Message-ID: <42D68C0B.9000106@RedHat.com> (raw)
In-Reply-To: <20050711092556.GD27163@suse.de>
Olaf Kirch wrote:
>
> #endif /* _LINUX_SUNRPC_XPRT_H */
> Index: linux-2.6.10/net/sunrpc/sysctl.c
> ===================================================================
> --- linux-2.6.10.orig/net/sunrpc/sysctl.c 2005-02-23 17:17:55.000000000 +0100
> +++ linux-2.6.10/net/sunrpc/sysctl.c 2005-02-23 17:19:35.000000000 +0100
> @@ -29,6 +29,10 @@ unsigned int nfs_debug;
> unsigned int nfsd_debug;
> unsigned int nlm_debug;
>
> +unsigned int xprt_min_resvport = 650;
> +unsigned int xprt_max_resvport = 1023;
> +
> +
> #ifdef RPC_DEBUG
>
> static struct ctl_table_header *sunrpc_table_header;
> @@ -121,6 +125,8 @@ done:
>
> static unsigned int min_slot_table_size = RPC_MIN_SLOT_TABLE;
> static unsigned int max_slot_table_size = RPC_MAX_SLOT_TABLE;
> +static unsigned int xprt_min_resvport_limit = 1;
> +static unsigned int xprt_max_resvport_limit = 65535;
Question, why is 65535 one being used here instead of something
like 1023 (or PROT_SOCK-1)? Since since inet_bind() will only
succeed with a source ports that are less than PROT_SOCK, so it
may not make sense to allow the user to set the max reserver port
to a value greater than PROT_SOCK-1, true?
steved.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-14 16:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 9:25 [PATCH] Fix xprt_bindresvport Olaf Kirch
2005-07-11 12:13 ` Trond Myklebust
2005-07-14 16:00 ` Steve Dickson [this message]
2005-07-16 7:11 ` Olaf Kirch
2005-07-17 11:36 ` Steve Dickson
2005-07-17 20:49 ` Peter Åstrand
-- strict thread matches above, loose matches on Subject: below --
2005-07-17 16:02 Lever, Charles
2005-07-17 16:45 ` Olaf Kirch
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=42D68C0B.9000106@RedHat.com \
--to=steved@redhat.com \
--cc=akpm@osdl.org \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.