From: "Magnus Naeslund\(f\)" <mag@fbab.net>
To: "Alexander Viro" <viro@math.psu.edu>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Maximum mountpoints + chrooted login
Date: Wed, 27 Jun 2001 13:56:50 +0200 [thread overview]
Message-ID: <008001c0ff00$448873d0$020a0a0a@totalmef> (raw)
In-Reply-To: <Pine.GSO.4.21.0106270422400.19655-100000@weyl.math.psu.edu>
From: "Alexander Viro" <viro@math.psu.edu>
>
[snip]
>
> I didn't go for proper solution in 2.4.0-test*). However, instead of
> crufting up kinda-sorta namespaces one could use the real thing. Relevant
> cleanups of superblock handling will go in in 2.5.very_early and the
> rest of patch (namespace proper) takes about 10Kb.
>
I'll wait for 2.5 then...
Where's that namespace patch located?
> You can simply say clone(CLONE_NAMESPACE,NULL) and you get an independent
> set of mounts to play with. mount/umount whatever you want before dropping
> the root priveleges. All children of that process will share its
namespace.
> When the last one goes away everything will be garbage-collected - no
> need to umount anything on logout.
>
Lovely!
>
> With the mntcache in - not really. It fixes the main performance problem.
Now in 2.4.5 it's darn slow to _unmount_, it's like 100 times faster to
mount than unmount :)
Cheers
Magnus Naeslund
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Programmer/Networker [|] Magnus Naeslund
PGP Key: http://www.genline.nu/mag_pgp.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-06-27 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 8:08 Magnus Naeslund(f)
2001-06-27 8:31 ` Alexander Viro
2001-06-27 11:56 ` Magnus Naeslund(f) [this message]
2001-06-27 14:46 ` Alexander Viro
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='008001c0ff00$448873d0$020a0a0a@totalmef' \
--to=mag@fbab.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®