linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, jtk@us.ibm.com,
	wtaber@us.ibm.com, pbadari@us.ibm.com, markv@us.ibm.com,
	gregkh@us.ibm.com, tytso@us.ibm.com, suparna@in.ibm.com
Subject: Re: [PATCH] fs: Restore files_lock and set_fs_root exports
Date: Thu, 13 Jan 2005 09:53:39 -0800	[thread overview]
Message-ID: <20050113175339.GE1269@us.ibm.com> (raw)
In-Reply-To: <1105601758.6031.6.camel@laptopd505.fenrus.org>

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

  reply	other threads:[~2005-01-13 17:56 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:05 [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-06 19:13 ` Christoph Hellwig
2005-01-06 20:07   ` Paul E. McKenney
2005-01-06 20:13     ` Christoph Hellwig
2005-01-06 20:35   ` Mike Waychison
2005-01-06 20:59     ` Christoph Hellwig
2005-01-06 21:35       ` Greg KH
2005-01-06 19:14 ` Al Viro
2005-01-06 20:13   ` Paul E. McKenney
2005-01-06 19:20 ` Arjan van de Ven
2005-01-06 20:15   ` Paul E. McKenney
2005-01-06 20:32     ` Al Viro
2005-01-06 21:04       ` Paul E. McKenney
2005-01-06 21:24         ` Al Viro
2005-01-06 23:26           ` Andrew Morton
2005-01-06 23:11             ` Alan Cox
2005-01-07  0:24               ` Linus Torvalds
2005-01-07  0:48                 ` Christoph Hellwig
2005-01-07  7:38                 ` Arjan van de Ven
2005-01-06 23:41             ` Christoph Hellwig
2005-01-07  0:29               ` Andrew Morton
2005-01-07  0:26                 ` Christoph Hellwig
2005-01-07  3:30                   ` Mike Waychison
2005-01-07  9:00                   ` Ingo Molnar
2005-01-07  9:15                     ` Christoph Hellwig
2005-01-07 12:14                       ` Antonio Vargas
2005-01-07 22:00                       ` Andrew Morton
2005-01-07 22:19                         ` Christoph Hellwig
2005-01-07 22:58                           ` Andrew Morton
2005-01-08 15:45                             ` Alan Cox
2005-01-07 22:49                         ` Alan Cox
2005-01-08  0:12                           ` Andrew Morton
2005-01-08  2:20                             ` Paul E. McKenney
2005-01-07 23:32                         ` Adrian Bunk
2005-01-08 13:10                           ` Al Viro
2005-01-07  1:34                 ` Alan Cox
2005-01-07  3:17                   ` Andrew Morton
2005-01-07  8:12                     ` Christoph Hellwig
2005-01-06 23:56             ` [PATCH] add feature-removal-schedule.txt documentation Greg KH
2005-01-07  0:23               ` Christoph Hellwig
2005-01-07  0:32                 ` Greg KH
2005-01-07 17:02               ` Randy.Dunlap
2005-01-07 17:54                 ` Linus Torvalds
2005-01-07 18:11                   ` Greg KH
2005-01-11 12:23                     ` [PATCH] cpufreq 2.4 interface removal schedule [Was: Re: [PATCH] add feature-removal-schedule.txt documentation] Dominik Brodowski
2005-01-12 18:41                       ` Greg KH
2005-01-07 23:58                 ` [PATCH] add feature-removal-schedule.txt documentation Dominik Brodowski
2005-01-12 18:41                 ` Greg KH
2005-01-08 18:32               ` Paul E. McKenney
2005-01-08 21:46                 ` Alan Cox
2005-01-08 23:03                   ` Arjan van de Ven
2005-01-09  6:23                     ` Paul E. McKenney
2005-01-09  6:27                   ` Paul E. McKenney
2005-01-07  2:02             ` [PATCH] fs: Restore files_lock and set_fs_root exports Paul E. McKenney
2005-01-07  1:01           ` Paul E. McKenney
2005-01-07  1:20             ` Al Viro
2005-01-13  2:51             ` Paul E. McKenney
2005-01-13  7:35               ` Arjan van de Ven
2005-01-13 17:53                 ` Paul E. McKenney [this message]
2005-01-13 17:07               ` Greg KH
2005-01-13 17:44                 ` Paul E. McKenney
2005-01-13 17:55                   ` Greg KH
2005-01-13 18:29                     ` Paul E. McKenney
2005-01-07  7:33         ` Arjan van de Ven
2005-01-07  8:15           ` Christoph Hellwig
2005-01-07 15:12           ` Paul E. McKenney
2005-01-07 15:23             ` Arjan van de Ven
2005-01-07 15:34               ` Paul E. McKenney
2005-01-07 15:56                 ` Arjan van de Ven

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=20050113175339.GE1269@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=gregkh@us.ibm.com \
    --cc=jtk@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markv@us.ibm.com \
    --cc=pbadari@us.ibm.com \
    --cc=suparna@in.ibm.com \
    --cc=tytso@us.ibm.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=wtaber@us.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).