All of
 help / color / mirror / Atom feed
From: (J. Bruce Fields)
To: Chuck Lever III <>
Cc: Neil Brown <>,
	Benjamin Coddington <>,
	Steve Dickson <>,
	Trond Myklebust <>,
	Linux NFS Mailing List <>
Subject: Re: [PATCH/RFC] NFSv4: ensure different netns do not share cl_owner_id
Date: Tue, 29 Mar 2022 11:11:41 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Mar 28, 2022 at 02:08:31PM +0000, Chuck Lever III wrote:
> Note also that the protocol allows a CLID_INUSE response to return
> the IP address of the conflicting client, but NFSD doesn't do that,
> I guess as a security measure.

The information disclosure sounds mild and not too surprising--mountd
already hands out information about v2/v3 clients (used by "showmount").

Chances are we just didn't get around to it.  If it'd help debug this
kind of problem, I think it'd be worth it.


      reply	other threads:[~2022-03-29 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  0:24 [PATCH/RFC] NFSv4: ensure different netns do not share cl_owner_id NeilBrown
2022-03-25 15:06 ` Chuck Lever III
2022-03-28  4:32   ` NeilBrown
2022-03-28 14:08     ` Chuck Lever III
2022-03-29 15:11       ` J. Bruce Fields [this message]

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:

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

  git send-email \ \ \ \ \ \ \ \ \

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.