mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Michał Zegan" <webczat_200@poczta.onet.pl>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Containers <containers@lists.linux-foundation.org>,
	linux-fsdevel@vger.kernel.org,
	Seth Forshee <seth.forshee@canonical.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] userns related vfs enhancements for v4.8
Date: Tue, 26 Jul 2016 19:02:24 -0500	[thread overview]
Message-ID: <8737mwne27.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <6ec55309-209d-7b90-9289-19e6fd180af9@poczta.onet.pl> (=?utf-8?Q?=22Micha=C5=82?= Zegan"'s message of "Wed, 27 Jul 2016 01:18:01 +0200")

Michał Zegan <webczat_200@poczta.onet.pl> writes:

> I have one question: what uids are written in the filesystem inodes?
> those that the kernel sees, or those mapped by user namespaces? and so,
> is it true that the filesystem will still require shifting uids,
> directly or indirectly, to be usable from inside user namespace? can't
> uids be mapped dynamically from what is in the inode to kernel uids
> based on the user namespace they are used from? Maybe because the fs can
> be mounted from outside before starting the container?

Feel free to read the code.  As best I can understand your question the
best answer is in reading and understanding the code yourself.

Eric

      reply	other threads:[~2016-07-27  0:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:44 Eric W. Biederman
2016-07-26 23:18 ` Michał Zegan
2016-07-27  0:02   ` Eric W. Biederman [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:
  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=8737mwne27.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seth.forshee@canonical.com \
    --cc=torvalds@linux-foundation.org \
    --cc=webczat_200@poczta.onet.pl \
    /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

Powered by JetHome