From: Alin Dobre <alin.dobre@elastichosts.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-fsdevel@vger.kernel.org,
containers@lists.linux-foundation.org,
v9fs-developer@lists.sourceforge.net,
Eric Van Hensbergen <ericvh@gmail.com>
Subject: Re: User namespace over 9p
Date: Tue, 27 May 2014 11:51:31 +0100 [thread overview]
Message-ID: <53846E33.4030601@elastichosts.com> (raw)
In-Reply-To: <87fvjvpksl.fsf@x220.int.ebiederm.org>
Eric, thanks for the response.
On 27/05/14 11:39, Eric W. Biederman wrote:
>> Do I understand this correctly as a problem, or does it work as
>> > intended? If latter, do you have any insights on how to achieve running
>> > containers in this scenario?
> If the permission check is made on the kernel with user namespaces we
> can reasonablly make it work. Otherwise we can not. That is a danger
> of using remote filesystems they can sometimes have weird arbitrary
> rules you were not expected.
>
I'm using diod as the 9p server, and it seems that it receives the
calling UID as -2 from the 9p kernel module on the client side, which
has user namespaces enabled.
Cheers,
Alin.
next prev parent reply other threads:[~2014-05-27 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 10:25 User namespace over 9p Alin Dobre
[not found] ` <53846804.6080408-1hSFou9RDDldEee+Cai+ZQ@public.gmane.org>
2014-05-27 10:39 ` Eric W. Biederman
2014-05-27 10:51 ` Alin Dobre [this message]
[not found] ` <87fvjvpksl.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2014-06-10 12:58 ` Alin Dobre
[not found] ` <539700EC.5010407-1hSFou9RDDldEee+Cai+ZQ@public.gmane.org>
2014-06-11 23:14 ` Eric W. Biederman
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=53846E33.4030601@elastichosts.com \
--to=alin.dobre@elastichosts.com \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=ericvh@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
/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).