Re: [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast

From: Steve Dickson <steved@redhat.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org, Petr Vorel <pvorel@suse.cz>
Subject: Re: [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast
Date: Mon, 18 Mar 2024 16:35:54 -0400	[thread overview]
Message-ID: <194e429f-0c73-4e6b-ae53-795406849669@redhat.com> (raw)
In-Reply-To: <171012164367.13576.5737075738433892235@noble.neil.brown.name>

On 3/10/24 9:47 PM, NeilBrown wrote:
> On Tue, 05 Mar 2024, Steve Dickson wrote:
>> Hey Neil,
>>
>> My apologies on addressing this...
>> Too much PTO :-)
>>
>> On 2/25/24 6:53 PM, NeilBrown wrote:
>>> The first two patches here I wrote some years ago but never posted - sorry.
>>> The third and fourth allow rpcbind to work with an abstract AF_UNIX
>>> address as preferentially used by recent kernels.
>>>
>>> NeilBrown
>>>
>>>
>>>    [PATCH 1/4] manpage: describe use of extra port for broadcast rpc
>>>    [PATCH 2/4] rpcbind: allow broadcast RPC to be disabled.
>> You realize that the broadcast code is configured out by default
>> ./configure  --help | grep rmt
>>     --enable-rmtcalls       Enables Remote Calls [default=no]
>>
>> So do we want to introduce a flag and man page section
>> for something that is off by default?
>>
> 
> Hmmm.... I guess I didn't know that when I wrote the patch - or forgot.
> 
> I wrote the patch a few years ago and found it when I was doing the
> abstract address stuff and though I better submit it.  I was wrong.
> 
> Please just ignore those first two patches.
Ignored... the last two patches were committed (tag: rpcbind-1_2_7-rc3)

steved.

> 
> Thanks,
> NeilBrown
> 