From: Peter Staubach <staubach@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Andrew Morton <akpm@osdl.org>,
SteveD@redhat.com, NFS@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: [NFS] Re: [PATCH] repair nfsd/sunrpc in 2.6.14-rc2-mm1 (and other -mm versions)
Date: Thu, 22 Sep 2005 16:08:57 -0400 [thread overview]
Message-ID: <43330F59.7080503@redhat.com> (raw)
In-Reply-To: <044B81DE141D7443BCE91E8F44B3C1E288E48E@exsvl02.hq.netapp.com>
Lever, Charles wrote:
>>Actually, Chuck's patch and Steve's aren't quite the same.
>>Both patches
>>fix the problem that the portmap daemon requires a request to
>>set something
>>to come from a reserved port. In addition to this, Steve's
>>patch reduces
>>the number of reserved ports that the kernel requires. This
>>is the problem
>>that resulted in pmap_create() being incorrectly modified in
>>the first
>>place.
>>Steve's patch correctly puts the support in rpc_getport()
>>where it belongs.
>>
>>
>
>mine does too. pmap_create() is used for both GET and SET, and i added
>a parm to allow pmap_create()'s caller to request a reserved port when
>needed.
>
Hmmm. That's not the patch that Andrew Morton included in his email to
linux-kernel then. That patch just removed the line to set xprt->resvport
to 0. That one fixed problem but not the other.
Thanx...
ps
next prev parent reply other threads:[~2005-09-22 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 19:53 [NFS] Re: [PATCH] repair nfsd/sunrpc in 2.6.14-rc2-mm1 (and other -mm versions) Lever, Charles
2005-09-22 20:08 ` Peter Staubach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-22 14:11 Lever, Charles
2005-09-22 19:31 ` Andrew Morton
2005-09-22 19:46 ` Peter Staubach
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=43330F59.7080503@redhat.com \
--to=staubach@redhat.com \
--cc=Charles.Lever@netapp.com \
--cc=NFS@lists.sourceforge.net \
--cc=SteveD@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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).