mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Serge Hallyn <serge.hallyn@ubuntu.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Andrey Vagin <avagin@openvz.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org, Andrey Vagin <avagin@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	Pavel Emelyanov <xemul@parallels.com>,
	Serge Hallyn <serge.hallyn@canonical.com>,
	Rob Landley <rob@landley.net>
Subject: Re: [PATCH] [RFC] mnt: add ability to clone mntns starting with the current root
Date: Tue, 07 Oct 2014 13:52:35 -0700	[thread overview]
Message-ID: <87wq8bvbzg.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20141007204627.GI28519@ubuntumail> (Serge Hallyn's message of "Tue, 7 Oct 2014 20:46:27 +0000")

Serge Hallyn <serge.hallyn@ubuntu.com> writes:

> Quoting Eric W. Biederman (ebiederm@xmission.com):
>> Al Viro <viro@ZenIV.linux.org.uk> writes:
>> 
>> 2> On Tue, Oct 07, 2014 at 02:30:40PM +0100, Al Viro wrote:
>> >> On Tue, Oct 07, 2014 at 04:12:57PM +0400, Andrey Vagin wrote:
>> >> > Another problem is that rootfs can't be hidden from a container, because
>> >> > rootfs can't be moved or umounted.
>> >> 
>> >> ... which is a bug in mntns_install(), AFAICS.
>> >
>> > Ability to get to exposed rootfs, that is.
>> 
>> The container side of this argument is pretty bogus.  It only applies
>> if user namespaces are not used for the container.
>
> User namespaces are still far too restricted for many container use
> cases.  We can't say "we have user namespaces so now privileged
> containers can be ignored".  Yes you never should have handed the
> keys to a privileged container to an untrusted person, but we do
> still try to protect the host from accidental damage due to a
> privileged container.

What I meant is that it isn't about containers.   It is about something
root can do.  So this is not a "container" problem.

>> So it is only root (and not root in a container) who can get to the
>> exposed rootfs.
>> 
>> I have a vague memory someone actually had a real use in miminal systems
>> for being able to get back to the rootfs and being able to use rootfs as
>> the rootfs.  There was even a patch at that time that Andrew Morton was
>> carrying for a time to allow unmounting root and get at rootfs, and to
>> prevent the oops on rootfs unmount in some way.
>> 
>> So not only do I not think it is a bug to get back too rootfs, I think
>> it is a feature that some people have expressed at least half-way sane
>> uses for.
>
> They can still do that if they want, using chroot :)

It would take fchdir or fchroot and a directory file descriptor open on
rootfs.  Frequently there is no appropriate directory file descriptor.

Eric

  reply	other threads:[~2014-10-07 20:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-07 12:12 Andrey Vagin
2014-10-07 13:30 ` Al Viro
2014-10-07 13:33   ` Al Viro
2014-10-07 19:44     ` Andrew Vagin
2014-10-07 20:30     ` Eric W. Biederman
2014-10-07 20:46       ` Serge Hallyn
2014-10-07 20:52         ` Eric W. Biederman [this message]
2014-10-07 21:32           ` Serge Hallyn
2014-10-07 21:42             ` Eric W. Biederman
2014-10-07 22:19               ` Andy Lutomirski
2014-10-07 22:42                 ` Eric W. Biederman
2014-10-07 22:44                   ` Andy Lutomirski
2014-10-07 23:42                     ` Eric W. Biederman
2014-10-07 23:44                       ` Andy Lutomirski
2014-10-08  0:20                         ` Eric W. Biederman
2014-10-08  0:25                           ` Andy Lutomirski
2014-10-07 21:02       ` Andy Lutomirski
2014-10-07 21:26         ` Eric W. Biederman
2014-10-07 21:38           ` Andy Lutomirski
2014-10-07 21:50             ` Eric W. Biederman
2014-10-07 21:52               ` Andy Lutomirski
2014-10-07 21:33         ` Serge Hallyn
2014-10-07 20:45 ` Eric W. Biederman
2014-10-08 11:08   ` Andrew Vagin
2014-10-08 15:35     ` Andy Lutomirski
2014-10-08 19:23       ` Eric W. Biederman
2014-10-08 19:31         ` Andy Lutomirski
2014-10-08 21:36           ` Rob Landley
2014-10-08 22:01             ` Andy Lutomirski
2014-10-08 23:38               ` Serge Hallyn
2014-10-08 23:41                 ` Andy Lutomirski
2014-10-08 21:23         ` Rob Landley
2014-10-09 10:29         ` Andrew Vagin

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=87wq8bvbzg.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@gmail.com \
    --cc=avagin@openvz.org \
    --cc=gorcunov@openvz.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=serge.hallyn@canonical.com \
    --cc=serge.hallyn@ubuntu.com \
    --cc=viro@ZenIV.linux.org.uk \
    --cc=xemul@parallels.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

Powered by JetHome