From: NeilBrown <neilb@suse.de>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, Petr Vorel <pvorel@suse.cz>
Subject: [PATCH 0/3 libtirpc] Support abstract addresses for rpcbind in libtirpc
Date: Mon, 26 Feb 2024 10:40:47 +1100 [thread overview]
Message-ID: <20240225234337.19744-1-neilb@suse.de> (raw)
I posted these patches in May 2023 at the same time as I posted patches
for the kernel to connect to an abstract address.
The kernel patches landed and I forgot to follow-up with these.
Thanks Petr for the reminder.
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 rpcbind
next reply other threads:[~2024-02-25 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 23:40 NeilBrown [this message]
2024-02-25 23:40 ` [PATCH 1/3] Allow working with abstract AF_UNIX addresses NeilBrown
2024-02-25 23:40 ` [PATCH 2/3] Change local_rpcb() to take a targaddr pointer NeilBrown
2024-03-09 14:27 ` Steve Dickson
2024-03-11 1:17 ` NeilBrown
2024-03-11 9:35 ` Petr Vorel
2024-02-25 23:40 ` [PATCH 3/3] Try using a new abstract address when connecting rpcbind NeilBrown
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=20240225234337.19744-1-neilb@suse.de \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=steved@redhat.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;
as well as URLs for NNTP newsgroup(s).