From: Ram Pai <linuxram@us.ibm.com> To: akpm@osdl.org, Al Viro <viro@parcelfarce.linux.theplanet.co.uk> Cc: Avantika Mathur <mathurav@us.ibm.com>, Mike Waychison <mike@waychison.com> Date: Mon, 25 Jul 2005 15:44:17 -0700 [thread overview] raw) , miklos@szeredi.hu, Janak Desai <janak@us.ibm.com>, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/7] shared subtree Hi Andrew/Al Viro, Enclosing a final set of well tested patches that implement Al Viro's shared subtree proposal. These patches provide the ability to mark a mount tree as shared/private/slave/unclone, along with the ability to play with these trees with operations like bind/rbind/move/pivot_root/namespace-clone etc. I believe this powerful feature can help build features like per-user namespace. Couple of projects may benefit from shared subtrees. 1) automounter for the ability to automount across namespaces. 2) SeLinux for implementing polyinstantiated trees. 3) MVFS for providing versioning file system. 4) FUSE for per-user namespaces? Thanks to Avantika for developing about 100+ test cases that tests various combintation of private/shared/slave/unclonable trees. All these tests have passed. I feel pretty confident about the stability of the code. The patches have been broken into 7 units, for ease of review. I realize that patch-3 'rbind.patch' is a bit heavier than all the other patches. The reason being, most of the shared-subtree functionality gets manifestated during bind/rbind operation. Couple of work items to be done are: 1. modify the mount command to support this feature eg: mount --make-shared /tmp 2. a tool that can help visualize the propogation tree, maybe support in /proc? 3. some documentation on how to use all this functionality. Please consider the patches for inclusion in your tree. The footprint of this code is pretty small in the normal code path where shared-subtree functionality is not used. Any suggestions/comments to improve the code is welcome. Thanks, RP
WARNING: multiple messages have this Message-ID (diff)
From: Ram Pai <linuxram@us.ibm.com> To: akpm@osdl.org, Al Viro <viro@parcelfarce.linux.theplanet.co.uk> Cc: Avantika Mathur <mathurav@us.ibm.com>, Mike Waychison <mike@waychison.com> Subject: (unknown) Date: Mon, 25 Jul 2005 15:44:17 -0700 [thread overview] Message-ID: <20050725224417.501066000@localhost> (raw) , miklos@szeredi.hu, Janak Desai <janak@us.ibm.com>, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH 0/7] shared subtree Hi Andrew/Al Viro, Enclosing a final set of well tested patches that implement Al Viro's shared subtree proposal. These patches provide the ability to mark a mount tree as shared/private/slave/unclone, along with the ability to play with these trees with operations like bind/rbind/move/pivot_root/namespace-clone etc. I believe this powerful feature can help build features like per-user namespace. Couple of projects may benefit from shared subtrees. 1) automounter for the ability to automount across namespaces. 2) SeLinux for implementing polyinstantiated trees. 3) MVFS for providing versioning file system. 4) FUSE for per-user namespaces? Thanks to Avantika for developing about 100+ test cases that tests various combintation of private/shared/slave/unclonable trees. All these tests have passed. I feel pretty confident about the stability of the code. The patches have been broken into 7 units, for ease of review. I realize that patch-3 'rbind.patch' is a bit heavier than all the other patches. The reason being, most of the shared-subtree functionality gets manifestated during bind/rbind operation. Couple of work items to be done are: 1. modify the mount command to support this feature eg: mount --make-shared /tmp 2. a tool that can help visualize the propogation tree, maybe support in /proc? 3. some documentation on how to use all this functionality. Please consider the patches for inclusion in your tree. The footprint of this code is pretty small in the normal code path where shared-subtree functionality is not used. Any suggestions/comments to improve the code is welcome. Thanks, RP
next reply other threads:[~2005-07-25 22:59 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-25 22:44 Ram Pai [this message] 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-27 19:54 ` [PATCH 1/7] shared subtree Miklos Szeredi 2005-07-27 21:39 ` Ram Pai 2005-07-28 7:35 ` mount behavior question Ram Pai 2005-07-28 11:56 ` Miklos Szeredi 2005-07-28 15:02 ` Ram Pai 2005-07-28 15:58 ` Miklos Szeredi 2005-07-28 18:22 ` Ram Pai 2005-07-28 19:30 ` Miklos Szeredi 2005-07-28 20:09 ` Ram Pai 2005-07-28 20:44 ` Miklos Szeredi 2005-07-28 20:59 ` Ram Pai 2005-07-28 18:27 ` Bryan Henderson 2005-07-28 19:01 ` Miklos Szeredi 2005-07-28 20:35 ` Bryan Henderson 2005-07-28 20:42 ` Ram Pai 2005-07-28 22:27 ` Bryan Henderson 2005-07-28 22:59 ` Ram Pai 2005-07-28 20:53 ` Miklos Szeredi 2005-07-28 22:51 ` Bryan Henderson 2005-07-28 9:57 ` [PATCH 1/7] shared subtree Miklos Szeredi 2005-07-29 19:54 ` Ram Pai 2005-07-30 5:39 ` Miklos Szeredi 2005-07-31 0:45 ` Ram Pai 2005-07-31 7:52 ` Miklos Szeredi 2005-07-31 8:25 ` Miklos Szeredi 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-27 19:13 ` [PATCH 3/7] shared subtree Miklos Szeredi 2005-07-27 20:30 ` Ram Pai 2005-07-28 8:34 ` Miklos Szeredi 2005-07-25 22:44 ` Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-25 22:44 ` Ram Pai 2005-07-25 22:44 ` (unknown) Ram Pai 2005-07-26 2:53 ` supposed to be shared subtree patches Ram Pai
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=20050725224417.501066000@localhost \ --to=linuxram@us.ibm.com \ --cc=akpm@osdl.org \ --cc=mathurav@us.ibm.com \ --cc=mike@waychison.com \ --cc=viro@parcelfarce.linux.theplanet.co.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.