From: Andy Lutomirski <luto@amacapital.net>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Seth Forshee <seth.forshee@canonical.com>,
Lukasz Pawelczyk <l.pawelczyk@samsung.com>,
Richard Weinberger <richard@nod.at>
Subject: [LSF/MM TOPIC] Filesystem namespaces and uid/gid/lsm remapping
Date: Tue, 2 Dec 2014 15:47:04 -0800 [thread overview]
Message-ID: <CALCETrVE2F2bcv4DjLOGL+R9Rn_4HEvRjifyOu1nA+gs7VgEeg@mail.gmail.com> (raw)
This should hopefully be a short topic, and it's possible that it'll
be settled by the time LSF/MM comes around, but:
There's a fair amount of interest from different directions for
allowing filesystems with a backing store to be mounted (in the
mount-from-scratch sense, not the bind-mount sense) in a user
namespace. For example, Seth has patches to allow unprivileged FUSE
mounts. There are a few issues here, for example:
- What happens to device nodes in those filesystems?
- If a FUSE backend is in a user namespace, how should UIDs be
translated to/from that backend?
- How should LSM security labels be translated?
- Should a struct super_block be associated with a user namespace?
(Answer: probably, I think.) If so, what should the semantics be?
There are also some remapping cases that aren't directly user
namespace-related. For example, I'd like to be able to insert
removable media and create files owned by uid 0 (or any other uid)
without actually being root.
--Andy
next reply other threads:[~2014-12-02 23:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 23:47 Andy Lutomirski [this message]
2014-12-03 3:37 ` [LSF/MM TOPIC] Filesystem namespaces and uid/gid/lsm remapping Eric W. Biederman
2015-02-22 17:12 ` [Lsf-pc] " James Bottomley
2015-02-23 12:38 ` Jan Kara
2014-12-03 14:48 ` Seth Forshee
2014-12-05 18:01 ` David Howells
2014-12-08 21:59 ` Eric W. Biederman
2014-12-09 18:51 ` [Lsf-pc] " Jeff Layton
2015-02-22 16:52 ` James Bottomley
2015-02-22 23:51 ` Jeff Layton
2015-02-22 17:01 ` James Bottomley
2015-02-23 15:54 ` Andy Lutomirski
2015-02-23 16:16 ` James Bottomley
2015-03-02 22:34 ` Andy Lutomirski
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=CALCETrVE2F2bcv4DjLOGL+R9Rn_4HEvRjifyOu1nA+gs7VgEeg@mail.gmail.com \
--to=luto@amacapital.net \
--cc=ebiederm@xmission.com \
--cc=l.pawelczyk@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=richard@nod.at \
--cc=seth.forshee@canonical.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).