Linux NFS development
 help / color / mirror / Atom feed
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>
Subject: [PATCH 0/2] Support abstract address for rpcbind in kernel
Date: Thu, 11 May 2023 08:06:24 +1000	[thread overview]
Message-ID: <168375610447.26246.3237443941479930060.stgit@noble.brown> (raw)

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


             reply	other threads:[~2023-05-10 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 22:06 NeilBrown [this message]
2023-05-10 22:06 ` [PATCH 1/2] SUNRPC: support abstract unix socket addresses NeilBrown
2023-05-10 22:06 ` [PATCH 2/2] SUNRPC: attempt to reach rpcbind with an abstract socket name NeilBrown
2023-05-23 12:17 ` [PATCH 0/2] Support abstract address for rpcbind in kernel Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=168375610447.26246.3237443941479930060.stgit@noble.brown \
    --to=neilb@suse.de \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nikita.yoush@cogentembedded.com \
    --cc=pvorel@suse.cz \
    --cc=steved@redhat.com \
    --cc=trond.myklebust@hammerspace.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox