From: Trond Myklebust <trondmy@hammerspace.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"sargun@sargun.me" <sargun@sargun.me>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: "kinglongmee@gmail.com" <kinglongmee@gmail.com>,
"Anna.Schumaker@Netapp.com" <Anna.Schumaker@Netapp.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>
Subject: Re: [PATCH] net/sunrpc: Add user namespace support
Date: Thu, 19 Jul 2018 19:45:50 +0000 [thread overview]
Message-ID: <e3988e150b5737e13f8b05ab25fd3ed3e5d42c14.camel@hammerspace.com> (raw)
In-Reply-To: <20180719174246.GA19824@ircssh-2.c.rugged-nimbus-611.internal>
On Thu, 2018-07-19 at 17:42 +0000, Sargun Dhillon wrote:
> This adds the ability to pass a non-init user namespace to
> rpcauth_create,
> via rpc_auth_create_args. If the specific authentication mechanism
> does not support non-init user namespaces, then it will return an
> error.
>
> Currently, the only two authentication mechanisms that support
> non-init user namespaces are auth_null, and auth_unix. auth_unix
> will send the UID / GID from the user namespace for authentication.
>
Firstly, please at least Cc the linux-nfs mailing list (as per the
MAINTAINERS file) when changing NFS and sunrpc code.
Secondly, can you please explain why we would want to use any user
namespace other than the one specified in the net namespace structure
(struct net) when communicating with network resources such as
rpc.gssd, the idmapper or, for that matter, the NFS server?
Thanks
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2018-07-19 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 17:42 [PATCH] net/sunrpc: Add user namespace support Sargun Dhillon
2018-07-19 19:45 ` Trond Myklebust [this message]
2018-07-20 0:00 ` Sargun Dhillon
2018-07-20 0:37 ` Trond Myklebust
2018-07-20 6:12 ` Sargun Dhillon
2018-07-20 11:48 ` Trond Myklebust
2018-07-20 17:06 ` Sargun Dhillon
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=e3988e150b5737e13f8b05ab25fd3ed3e5d42c14.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=ebiederm@xmission.com \
--cc=kinglongmee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sargun@sargun.me \
/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).