From: Rob Landley <rob@landley.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/5] initmpfs: replace MS_NOUSER in initramfs
Date: Sat, 29 Jun 2013 22:09:20 -0500 [thread overview]
Message-ID: <1372561760.2776.161@driftwood> (raw)
In-Reply-To: <87y59swg8z.fsf@xmission.com> (from ebiederm@xmission.com on Sat Jun 29 20:15:40 2013)
On 06/29/2013 08:15:40 PM, Eric W. Biederman wrote:
> Rob Landley <rob@landley.net> writes:
>
> > From: Rob Landley <rob@landley.net>
> >
> > Mounting MS_NOUSER prevents --bind mounts from rootfs. Prevent new
> rootfs
> > mounts with a different mechanism that doesn't affect bind mounts.
>
> I don't see patches 4 and 5 so I don't know if you have covered this
> elsewhere but a very important part of the reason for MS_NOUSER is to
> prevent unmounting of rootfs.
>
> The entire vfs breaks if you are allowed to unmount rootfs, and it
> appears this patch is allowing that.
I mean I tried "mount --move / home". (--bind worked.)
Long day...
Rob
next prev parent reply other threads:[~2013-06-30 3:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 20:12 [PATCH 0/5] initmpfs: use tmpfs instead of ramfs for rootfs Rob Landley
2013-06-29 20:12 ` [PATCH 1/5] initmpfs: replace MS_NOUSER in initramfs Rob Landley
2013-06-30 1:15 ` Eric W. Biederman
2013-06-30 2:45 ` Rob Landley
2013-06-30 3:09 ` Rob Landley [this message]
2013-06-29 20:12 ` [PATCH 2/5] initmpfs: Move bdi setup from init_rootfs to init_ramfs Rob Landley
2013-06-29 20:12 ` [PATCH 3/5] initmpfs: Move rootfs code from fs/ramfs/ to init/ Rob Landley
2013-06-29 20:12 ` [PATCH 4/5] initmpfs: Make rootfs use tmpfs when CONFIG_TMPFS enabled Rob Landley
2013-06-29 20:12 ` [PATCH 5/5] initmpfs: Use initramfs if rootfstype= or root= specified Rob Landley
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=1372561760.2776.161@driftwood \
--to=rob@landley.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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