Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: [PATCH 0/3] Support abstract addresses for rpcbind in libtirpc
From:   NeilBrown <neilb@suse.de>
To:     Jeff Layton <jlayton@kernel.org>,
        Trond Myklebust <trond.myklebust@hammerspace.com>
Cc:     linux-nfs@vger.kernel.org, Petr Vorel <pvorel@suse.cz>,
        Nikita Yushchenko <nikita.yoush@cogentembedded.com>,
        Steve Dickson <steved@redhat.com>
Date:   Thu, 11 May 2023 08:20:45 +1000
Message-ID: <168375715312.25049.2010665843445641504.stgit@noble.brown>
User-Agent: StGit/1.5
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

To accompany the kernel patches, these patches enhance libtirpc to work
with abstract addresses, and to attempt to reach rpcbind using the
proposed new abstract address: "\0/run/rpcbind.sock"

NeilBrown


---

NeilBrown (3):
      Allow working with abstract AF_UNIX addresses.
      Change local_rpcb() to take a targaddr pointer.
      Try using a new abstract address when connecting rpcbind


 src/rpc_com.h         |   6 +++
 src/rpc_generic.c     |  18 ++++---
 src/rpc_soc.c         |   6 ++-
 src/rpcb_clnt.c       | 112 ++++++++++++++++++++++--------------------
 tirpc/rpc/rpcb_prot.h |   1 +
 tirpc/rpc/rpcb_prot.x |   1 +
 6 files changed, 85 insertions(+), 59 deletions(-)

--
Signature