On Thu, Jul 17, 2008 at 10:47:25AM -0400, Chuck Lever wrote:
> On Wed, Jul 16, 2008 at 3:06 PM, J. Bruce Fields <[email protected]> wrote:
> > The immediate problem seems like a kernel bug to me--it seems to me that
> > the calls to local daemons should be ignoring {min_,max}_resvport. (Or
> > is there some way the daemons can still know that those calls come from
> > the local kernel?)
>
> I tend to agree. The rpcbind client (at least) does specifically
> require a privileged port, so a large min/max port range would be out
> of the question for those rpc_clients.
Any chance I could talk you into doing a patch for that?
--b.
On Thu, Jul 17, 2008 at 10:48 AM, J. Bruce Fields <[email protected]> wrote:
> On Thu, Jul 17, 2008 at 10:47:25AM -0400, Chuck Lever wrote:
>> On Wed, Jul 16, 2008 at 3:06 PM, J. Bruce Fields <[email protected]> wrote:
>> > The immediate problem seems like a kernel bug to me--it seems to me that
>> > the calls to local daemons should be ignoring {min_,max}_resvport. (Or
>> > is there some way the daemons can still know that those calls come from
>> > the local kernel?)
>>
>> I tend to agree. The rpcbind client (at least) does specifically
>> require a privileged port, so a large min/max port range would be out
>> of the question for those rpc_clients.
>
> Any chance I could talk you into doing a patch for that?
I can look at it when I get back next week.
--
"Alright guard, begin the unnecessarily slow-moving dipping mechanism."
--Dr. Evil