Re: [PATCH] fs: Restore files_lock and set_fs_root exports

[Paul E. McKenney]

On Thu, Jan 13, 2005 at 08:35:58AM +0100, Arjan van de Ven wrote:
> On Wed, 2005-01-12 at 18:51 -0800, Paul E. McKenney wrote:
> > On Thu, Jan 06, 2005 at 05:01:19PM -0800, Paul E. McKenney wrote:
> > > On Thu, Jan 06, 2005 at 09:24:17PM +0000, Al Viro wrote:
> > > > "Use recursive bindings instead of trying to take over the entire mount tree
> > > > and mirroring it within your fs code.  And do that explicitly from userland".
> > > 
> > > Thank you for the pointer!  By this, you mean do mount operations in
> > > conjunction with namespaces, right?
> > > 
> > > I will follow up with more detail as I learn more.  The current issue
> > > seems to be with removeable devices.  Their users want to be accessing
> > > a particular version, but still see a memory stick that was subsequently
> > > mounted outside of the view.  Straightforward use of mounts and namespaces
> > > would prevent the memory stick from being visible to users that were
> > > already in view.
> > 
> > OK, after much thrashing, here is what the ClearCase users need.
> > Sorry for the length -- the first few paragraphs gives the flavor of
> > it and the rest goes into more detail with examples.
> > 
> > Thoughts?
> > 
> 
> Interesting; so clearcase mvfs currently extends the linux VFS to do all
> this.... It would be very interesting to get these extensions to linux
> posted on this mailing list in patch form, since it could well be a nice
> generic enhancement of linux. (Assuming Al doesn't go WTF over the code
> of course :-)

Just given the interfaces it makes use of, I would guess that Al would
more than go WTF over the current code.  Most would probably say that the
current code does not extend Linux VFS, but rather subverts it.  Plus it
was written by people without any history of Linux-kernel development,
so one would anticipate much heartburn over style and usage issues.  ;-)

All that aside, if you really really want to see it, I will see what I
can do about getting it to you.

							Thanx, Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/