linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Rob Landley <rob@landley.net>
Cc: Ram Pai <linuxram@us.ibm.com>, Miklos Szeredi <miklos@szeredi.hu>,
	Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 12/18] shared mount handling: bind and rbind
Date: Tue, 15 Nov 2005 19:53:36 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0511151948570.13959@g5.osdl.org> (raw)
In-Reply-To: <200511152129.04079.rob@landley.net>



On Tue, 15 Nov 2005, Rob Landley wrote:
> 
> The || fallback in the third part won't work.  chroot(".") will get you to the 
> new filesystem, but chdir("/") still gets you to the old one, even though 
> we've overmounted it.  (I have no idea why.  I assume it's because / is 
> special.)

'/' is special exactly the same way '.' is: one is shorthand for "current 
process' root", and the other is shorthand for "current process' cwd".

So if you mount over '/', it won't actually do what you think it does: 
because when you open "/", it will continue to open the _old_ "/". Exactly 
the same way that mounting over somebody's cwd won't do what you think it 
does - because the root and the cwd have been looked-up earlier and are 
cached with the process.

This is why we have "pivot_root()" and "chroot()", which can both be used 
to do what you want to do. You mount the new root somewhere else, and then 
you chroot (or pivot-root) to it. And THEN you do 'chdir("/")' to move the 
cwd into the new root too (and only at that point have you "lost" the old 
root - although you can actually get it back if you have some file 
descriptor open to it).

		Linus

  reply	other threads:[~2005-11-16  3:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08  2:01 [PATCH 12/18] shared mount handling: bind and rbind Al Viro
2005-11-08 14:11 ` Miklos Szeredi
2005-11-08 15:48   ` Ram Pai
2005-11-08 15:55     ` Miklos Szeredi
2005-11-09 18:44       ` Ram Pai
2005-11-09 18:59         ` Linus Torvalds
2005-11-09 19:26           ` Al Viro
2005-11-09 19:28           ` Ram Pai
2005-11-16  3:29           ` Rob Landley
2005-11-16  3:53             ` Linus Torvalds [this message]
2005-11-16  5:35               ` Al Boldi
2005-11-16  8:19                 ` Miklos Szeredi
2005-11-16  9:10                   ` Rob Landley
2005-11-16 10:14                     ` Miklos Szeredi
2005-11-16 13:59                   ` Shaya Potter
2005-11-16 16:35                     ` Miklos Szeredi
2005-11-16 20:05                     ` Al Boldi
2005-11-16 20:21                       ` Shaya Potter
2005-11-16  8:47                 ` Rob Landley
2005-11-16  8:41               ` Rob Landley
2005-11-16 16:18                 ` Linus Torvalds
2005-11-09 10:54 ` Miklos Szeredi
2005-11-09 14:31   ` Al Viro
2005-11-09 15:22     ` Miklos Szeredi
2005-11-09 15:56       ` Al Viro
2005-11-09 16:33         ` Miklos Szeredi

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=Pine.LNX.4.64.0511151948570.13959@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@us.ibm.com \
    --cc=miklos@szeredi.hu \
    --cc=rob@landley.net \
    --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;
as well as URLs for NNTP newsgroup(s).