Received-SPF: pass (google.com: domain of linux-nfs+bounces-2257-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
MIME-Version: 1.0
From: "NeilBrown" <neilb@suse.de>
To: "Steve Dickson" <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, "Petr Vorel" <pvorel@suse.cz>
Subject:
 Re: [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast
In-reply-to: <b4b4d325-f15f-4fb3-a52c-c3f39d56018a@redhat.com>
References: <20240225235628.12473-1-neilb@suse.de>,
 <b4b4d325-f15f-4fb3-a52c-c3f39d56018a@redhat.com>
Date: Mon, 11 Mar 2024 12:47:23 +1100
Message-id: <171012164367.13576.5737075738433892235@noble.neil.brown.name>

On Tue, 05 Mar 2024, Steve Dickson wrote:
> Hey Neil,
>=20
> My apologies on addressing this...
> Too much PTO :-)
>=20
> On 2/25/24 6:53 PM, NeilBrown wrote:
> > The first two patches here I wrote some years ago but never posted - sorr=
y.
> > The third and fourth allow rpcbind to work with an abstract AF_UNIX
> > address as preferentially used by recent kernels.
> >=20
> > NeilBrown
> >=20
> >=20
> >   [PATCH 1/4] manpage: describe use of extra port for broadcast rpc
> >   [PATCH 2/4] rpcbind: allow broadcast RPC to be disabled.
> You realize that the broadcast code is configured out by default
> ./configure  --help | grep rmt
>    --enable-rmtcalls       Enables Remote Calls [default=3Dno]
>=20
> So do we want to introduce a flag and man page section
> for something that is off by default?
>=20

Hmmm.... I guess I didn't know that when I wrote the patch - or forgot.=20

I wrote the patch a few years ago and found it when I was doing the
abstract address stuff and though I better submit it.  I was wrong.

Please just ignore those first two patches.

Thanks,
NeilBrown