Messages in this thread | | | Subject | Re: [PATCH 00/20] Mount writer count and read-only bind mounts (v3) | From | Arjan van de Ven <> | Date | Wed, 28 Jun 2006 10:42:07 +0200 |
| |
On Tue, 2006-06-27 at 19:17 -0700, Andrew Morton wrote: > On Tue, 27 Jun 2006 18:50:36 -0700 > Dave Hansen <haveblue@us.ibm.com> wrote: > > > > > Since the last revision, the locking in faccessat() and > > > > mnt_is_readonly() has been changed to fix a race which might have > > > > caused a false-negative mount-is-readonly return when faccessat() > > > > is called while another two processes are racing to make a mount > > > > readonly. > > > > > > > umm, what's it all for? > > > > Mostly for vserver, for now. They allow a filesystem to be r/w, but > > have r/o views into it. This is really handy so that every vserver can > > use a common install but still allow the administrator to update it. > > OK. That makes it one of those features which stays in -mm until we work > out what we're going to do about containers/vserver/etc. > > Unless there's something else which needs it?
in a previous life we repeatedly had customers who really wanted this. It's more than just containers; it's chroots too (arguably that's containers as well but a lot more common deployed today) but also things where the customer wanted to mount a part of a network mount as /usr, but read only just to be sure....
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |