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 addresses for rpcbind in rpcbind
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:27:36 +1000
Message-ID: <168375751051.30997.11634044913854205425.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

If the previous patch sets to the kernel and the libtirpc are accepted,
we need rpcbind to listen on the new abstract address.

We could unconditionally listen, but as current libtirpc rejects sockets
bound to abstract addresses, this would result in unsightly errors.

So only add the new ListenStream to rpcbind.socket if it is likely to
work.

Also enhance rpcinfo to use the new abstract address if possible.

NeilBrown

---

NeilBrown (2):
      Listen on an AF_UNIX abstract address if supported.
      rpcinfo: try connecting using abstract address.


 configure.ac              | 13 ++++++++++++-
 src/rpcinfo.c             | 24 +++++++++++++++++++++++-
 systemd/rpcbind.socket    | 18 ------------------
 systemd/rpcbind.socket.in | 19 +++++++++++++++++++
 4 files changed, 54 insertions(+), 20 deletions(-)
 delete mode 100644 systemd/rpcbind.socket
 create mode 100644 systemd/rpcbind.socket.in

--
Signature