Received-SPF: pass (google.com: domain of linux-nfs+bounces-2171-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:40f1:3f00::1 as permitted sender) client-ip=2604:1380:40f1:3f00::1;
Message-ID: <b4b4d325-f15f-4fb3-a52c-c3f39d56018a@redhat.com>
Date: Mon, 4 Mar 2024 11:51:15 -0500
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH 0/4 rpcbind] Supprt abstract addresses and disable
 broadcast
Content-Language: en-US
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org, Petr Vorel <pvorel@suse.cz>
References: <20240225235628.12473-1-neilb@suse.de>
From: Steve Dickson <steved@redhat.com>
In-Reply-To: <20240225235628.12473-1-neilb@suse.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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?

steved.
>   [PATCH 3/4] Listen on an AF_UNIX abstract address if supported.
>   [PATCH 4/4] rpcinfo: try connecting using abstract address.
>