From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>,
stgraber@ubuntu.com, apw@canonical.com
Subject: overlayfs mounts in user namespaces
Date: Mon, 10 Feb 2014 20:51:33 +0100 [thread overview]
Message-ID: <20140210195133.GA10107@mail.hallyn.com> (raw)
Hi Eric,
most filesystems cannot be mounted in a non-init user namespace because we
don't trust the superblock parsers to DTRT when handed garbage. I was
wondering if you had any ideas on ways that allowing root in a non-init userns
to mount an overlayfs fs would be dangerous? There's no superblock parsing in
that case at all; writes end up being allowed if and only if the userid owning
the 'upper' (writeable) layer is mapped into the userns. Near as I can tell
it should be quite safe. But my imagination isn't the most active.
I assume there would be concerns about memory usage if the system is not
configured to place all logged-in users into configured cgroups? Is there
anything else you can think of that could be abused?
(I realize overlayfs isn't upstream yet so the question may not be all that
interesting to most people...)
thanks,
-serge
next reply other threads:[~2014-02-10 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 19:51 Serge E. Hallyn [this message]
2014-02-10 21:39 ` overlayfs mounts in user namespaces 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=20140210195133.GA10107@mail.hallyn.com \
--to=serge@hallyn.com \
--cc=apw@canonical.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stgraber@ubuntu.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