Received-SPF: pass (google.com: domain of linux-nfs+bounces-2379-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: <6413ab2a-6629-4b5d-95ae-53bc790d132e@redhat.com>
Date: Mon, 18 Mar 2024 16:39:32 -0400
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH 0/3 libtirpc v2] Support abstract addresses for rpcbind in
 libtirpc
Content-Language: en-US
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
References: <20240311014327.19692-1-neilb@suse.de>
From: Steve Dickson <steved@redhat.com>
In-Reply-To: <20240311014327.19692-1-neilb@suse.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


On 3/10/24 9:41 PM, NeilBrown wrote:
> This resend includes a couple of bug fixes.
> In the first patch, __rpc_taddr2uaddr_af() was reported a "universal" address
> of the absract socket as starting with "\0" instead of "@".
> 
> In the second patch, only one local_rpcb() call wants the target address.
> 
> Thanks,
> NeilBrown
> 
>   [PATCH 1/3] Allow working with abstract AF_UNIX addresses.
>   [PATCH 2/3] Change local_rpcb() to take a targaddr pointer.
>   [PATCH 3/3] Try using a new abstract address when connecting to
> 
Committed... (tag: libtirpc-1-3-5-rc3)

steved.