linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "bfields@fieldses.org" <bfields@fieldses.org>,
	"schumakeranna@gmail.com" <schumakeranna@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"dai.ngo@oracle.com" <dai.ngo@oracle.com>,
	"steved@redhat.com" <steved@redhat.com>,
	"olga.kornievskaia@gmail.com" <olga.kornievskaia@gmail.com>,
	"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: server-to-server copy by default
Date: Thu, 21 Oct 2021 14:22:13 +0000	[thread overview]
Message-ID: <aec219339d8296b7e9b114d9d247a71fd47423c5.camel@hammerspace.com> (raw)
In-Reply-To: <20211021141329.GC25711@fieldses.org>

On Thu, 2021-10-21 at 10:13 -0400, Bruce Fields wrote:
> On Wed, Oct 20, 2021 at 07:04:53PM +0000, Chuck Lever III wrote:
> > Unprivileged mounting seems like a different question to me.
> > Related, possibly, but not the same. I'd rather leave that
> > discussion to another thread.
> 
> Well, I'd be curious if client maintainers have any thoughts.
> 
> The NFS client still disallows unprivileged mounts, right?  Is it
> something you think could be supported, and if so, do you have an
> idea
> what's left to do?
> 
> Trond, I remember asking you about unprivileged mounts at a bakeathon
> a
> few years ago, and at the time you seemed to think it'd be a
> reasonable
> thing to do eventually, and the one obstacle you mentioned was that
> the
> client wasn't capable of maintaining separate state in different
> namespaces.  That's fixed, isn't it?
> 

Yes, that's mostly fixed. As far as I'm concerned, there should be no
major obstacles to allowing unprivileged mounts in their own private
net namespace.
The one thing to note, though, is that AUTH_SYS still required that the
container be given a CAP_NET_BIND_SERVICE privilege to allow binding to
a privileged port.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2021-10-21 14:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 15:54 server-to-server copy by default J. Bruce Fields
2021-10-20 16:00 ` Chuck Lever III
2021-10-20 16:33   ` Olga Kornievskaia
2021-10-20 19:03     ` dai.ngo
2021-10-20 20:29       ` Bruce Fields
2021-10-21  5:00         ` dai.ngo
2021-10-21 14:02           ` Bruce Fields
2021-10-22  6:34             ` dai.ngo
2021-10-22 12:58               ` Bruce Fields
2021-11-01 17:37               ` dai.ngo
2021-11-01 19:33                 ` Bruce Fields
2021-11-01 19:55                   ` dai.ngo
2021-10-20 17:24   ` Steve Dickson
2021-10-20 17:51     ` Chuck Lever III
2021-10-20 16:37 ` Olga Kornievskaia
2021-10-20 17:45   ` Chuck Lever III
2021-10-20 18:15     ` Bruce Fields
2021-10-20 19:04       ` Chuck Lever III
2021-10-21 13:43         ` Steve Dickson
2021-10-21 13:56         ` Bruce Fields
2021-10-21 14:13         ` Bruce Fields
2021-10-21 14:22           ` Trond Myklebust [this message]
2021-10-21 14:38             ` bfields
2021-10-20 18:00   ` J. Bruce Fields
2021-11-01 18:22 ` Charles Hedrick
2021-11-01 19:25   ` Steve Dickson
2021-11-01 19:44     ` Charles Hedrick

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=aec219339d8296b7e9b114d9d247a71fd47423c5.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=olga.kornievskaia@gmail.com \
    --cc=schumakeranna@gmail.com \
    --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).