From: Rob Landley <landley@trommello.org>
To: Christoph Hellwig <hch@infradead.org>, Kenneth Johansson <ken@kenjo.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Andreas Haumer <andreas@xss.co.at>,
linux-kernel@vger.kernel.org, willy@w.ods.org
Subject: Re: rootfs exposure in /proc/mounts
Date: Sun, 27 Oct 2002 20:17:32 -0500 [thread overview]
Message-ID: <200210271917.32650.landley@trommello.org> (raw)
In-Reply-To: <20021028001831.A31614@infradead.org>
On Sunday 27 October 2002 18:18, Christoph Hellwig wrote:
> On Mon, Oct 28, 2002 at 01:03:28AM +0100, Kenneth Johansson wrote:
> > On Sun, 2002-10-27 at 16:09, Christoph Hellwig wrote:
> > > you might have very different mounts in different processes.
> >
> > You can ?? apart from chroot that can make things interesting how do
> > you do this?
>
> clone(..., CLONE_NEWNS, ...)
>
> After that subsequent namespace operations will only affect your process
> and it's child processes.
Cool.
Question: if those processes mount something and then exit, does that
something get unmounted automatically or is this a mount point leak?
Rob
--
http://penguicon.sf.net - Terry Pratchett, Eric Raymond, Pete Abrams, Illiad,
CmdrTaco, liquid nitrogen ice cream, and caffienated jello. Well why not?
next prev parent reply other threads:[~2002-10-28 6:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 18:53 rootfs exposure in /proc/mounts Andreas Steinmetz
2002-10-26 18:59 ` Alexander Viro
2002-10-26 19:12 ` Andreas Steinmetz
2002-10-26 19:26 ` Jeff Garzik
2002-10-27 0:22 ` Andreas Steinmetz
2002-10-27 10:21 ` Andreas Haumer
2002-10-27 11:18 ` Willy Tarreau
2002-10-27 23:27 ` Michal Jaegermann
2002-10-28 9:05 ` Kasper Dupont
2002-10-27 15:02 ` Jeff Garzik
2002-10-27 15:09 ` Christoph Hellwig
2002-10-28 0:03 ` Kenneth Johansson
2002-10-28 0:18 ` Christoph Hellwig
2002-10-28 1:17 ` Rob Landley [this message]
2002-10-28 15:01 ` Christoph Hellwig
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=200210271917.32650.landley@trommello.org \
--to=landley@trommello.org \
--cc=andreas@xss.co.at \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.com \
--cc=ken@kenjo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.org \
/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