Messages in this thread | | | Subject | Re: [PATCH 21/22] honor r/w changes at do_remount() time | From | Dave Hansen <> | Date | Fri, 09 Feb 2007 16:00:57 -0800 |
| |
On Fri, 2007-02-09 at 15:22 -0800, Andrew Morton wrote: > On Fri, 09 Feb 2007 14:53:44 -0800 > Dave Hansen <hansendc@us.ibm.com> wrote: > > > This is the core of the read-only bind mount patch set. > > Who wants read-only bind mounts, and for what reason?
The original desire came out of the linux-vserver project. It allows a sysadmin to share directories between many vservers/containers and keep those containers from writing to it, even though the users in that vserver may have "root" privileges.
This also has the advantage of cleaning up the somewhat hackish "look for writable-open-files during remount/ro operations". It should also allow us to separate the concepts of the user wanting a filesystem to be r/o and the filesystem _itself_ being r/o because of a r/o device or some kind of corruption.
-- Dave
- 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/
| |