linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Steve Dickson <steved@redhat.com>
Cc: NeilBrown <neilb@suse.de>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast
Date: Mon, 4 Mar 2024 19:29:31 +0100	[thread overview]
Message-ID: <20240304182931.GA3408054@pevik> (raw)
In-Reply-To: <b4b4d325-f15f-4fb3-a52c-c3f39d56018a@redhat.com>

Hi Neil, Steve,

> Hey Neil,

> My apologies on addressing this...
> Too much PTO :-)

> On 2/25/24 6:53 PM, NeilBrown wrote:
> > The first two patches here I wrote some years ago but never posted - sorry.
> > The third and fourth allow rpcbind to work with an abstract AF_UNIX
> > address as preferentially used by recent kernels.

> > NeilBrown


> >   [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=no]

> So do we want to introduce a flag and man page section
> for something that is off by default?

I would say man page does not harm.

If I'm not mistaken, it's disabled in openSUSE and Debian/Ubuntu, maybe
disabling flag is really not needed.

Kind regards,
Petr

> steved.
> >   [PATCH 3/4] Listen on an AF_UNIX abstract address if supported.
> >   [PATCH 4/4] rpcinfo: try connecting using abstract address.



  reply	other threads:[~2024-03-04 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 23:53 [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast NeilBrown
2024-02-25 23:53 ` [PATCH 1/4] manpage: describe use of extra port for broadcast rpc NeilBrown
2024-02-25 23:53 ` [PATCH 2/4] rpcbind: allow broadcast RPC to be disabled NeilBrown
2024-03-04 18:32   ` Petr Vorel
2024-03-04 18:42     ` Roland Mainz
2024-02-25 23:53 ` [PATCH 3/4] Listen on an AF_UNIX abstract address if supported NeilBrown
2024-03-04 18:42   ` Petr Vorel
2024-02-25 23:53 ` [PATCH 4/4] rpcinfo: try connecting using abstract address NeilBrown
2024-03-04 18:58   ` Petr Vorel
2024-03-04 16:51 ` [PATCH 0/4 rpcbind] Supprt abstract addresses and disable broadcast Steve Dickson
2024-03-04 18:29   ` Petr Vorel [this message]
2024-03-04 20:32     ` Steve Dickson
2024-03-11  1:47   ` NeilBrown
2024-03-18 20:35     ` Steve Dickson

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=20240304182931.GA3408054@pevik \
    --to=pvorel@suse.cz \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --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).