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/2] Support abstract address for rpcbind in kernel
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:06:24 +1000
Message-ID: <168375610447.26246.3237443941479930060.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

These two patches cause the SUNRPC layer in Linux to attempt to contact
rpcbind using an AF_UNIX socket with an abstract address before
the existing attempts of AF_UNIX to a socket in the filesystem, and IP
to a well known port.

This allows the benefits of an AF_UNIX connection combined with the
benefits of honouring the network namespace when connection rpcbind.

For this to be useful, rpcbind must listed on that name, and user-space
tools must also connect to the same address.  This requires changes to
rpcbind and too libtirpc.  libtirpc currently has a bug which causes
sockets bountd to abstract addresses to appear to be unbound, so asking
systemd to pass rpcbind an abstract socket doesn't work - rpcbind
rejects it.

Patches for rpcbind and libtirpc will follow.

NeilBrown


---

NeilBrown (2):
      SUNRPC: support abstract unix socket addresses
      SUNRPC: attempt to reach rpcbind with an abstract socket name


 net/sunrpc/clnt.c      |  8 ++++++--
 net/sunrpc/rpcb_clnt.c | 39 +++++++++++++++++++++++++++++++--------
 net/sunrpc/xprtsock.c  |  9 +++++++--
 3 files changed, 44 insertions(+), 12 deletions(-)

--
Signature