public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Neil Brown <neilb@suse.de>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: pivot_root broken in 2.6.15-rc1-mm2
Date: Wed, 23 Nov 2005 06:02:52 -0600	[thread overview]
Message-ID: <200511230602.53960.rob@landley.net> (raw)
In-Reply-To: <17283.56197.347658.787608@cse.unsw.edu.au>

On Tuesday 22 November 2005 21:01, Neil Brown wrote:
> Ah, OK.
> It's just that pivot_root works in this context in 2.6.11.9, so I
> figured it was a breakage.

And if you then umount the ramfs you just pivoted, the kernel locks hard.

That was a bug.

What you're looking for is switch_root, which has variants buried in klib, or 
in the current CVS version of busybox, or glued into Red Hat's weird little 
multi-function ramdisk shell, and probably a few other places by now.

Rather than unmounting rootfs, it deletes everything out of it to free up the 
space.  (It basically does the functional equivalent of "find / -xdev | xargs 
rm -rf", overmounts the old root with the new root, does a chroot, and execs 
the new init out of the new root.  Actually getting it right's a bit tricky, 
of course.  I still need to test the busybox version a whole lot more.  It's 
on my to-do list...)

Rob

  reply	other threads:[~2005-11-23 12:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  2:07 pivot_root broken in 2.6.15-rc1-mm2 Neil Brown
2005-11-23  2:15 ` Al Viro
2005-11-23  2:38   ` Johannes Stezenbach
2005-11-23  3:01   ` Neil Brown
2005-11-23 12:02     ` Rob Landley [this message]
2005-11-25 11:52       ` Nix
2005-11-25 13:16         ` Rob Landley
2005-11-25 15:32           ` Nix
2005-11-23 11:43 ` Rob Landley
2005-11-24  5:09   ` Neil Brown
2005-11-24  5:54     ` [PATCH] " Rob Landley
2005-11-25 11:53   ` Nix

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=200511230602.53960.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=viro@ftp.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