public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [RFC PATCH] file as directory
Date: Wed, 23 May 2007 16:06:02 +0100	[thread overview]
Message-ID: <20070523150602.GZ4095@ftp.linux.org.uk> (raw)
In-Reply-To: <E1HqrtF-0002Fb-00@dorka.pomaz.szeredi.hu>

On Wed, May 23, 2007 at 04:32:37PM +0200, Miklos Szeredi wrote:
> > Umm...  It is related to detached subtrees, but I'm not sure if it is what
> > you are thinking about.
> 
> I was thinking of a similar one by Mike Waychison.  It had the problem
> of requiring a spinlock for mntget/mntput.  It was also different in
> that it did not gradually dissolve detached trees, but kept them as
> whole blobs until the last ref went away.
 
Here the spinlock is needed only when mnt_busy goes to 0, so presumably
it won't be a serious problem on more or less common setups; however,
it certainly would need serious profiling.

> How will this work with copy_tree() and namespace duplication, which
> currently walk the tree with only namespace_sem held?

Easy - grab namespace_sem, grab vfsmount_lock, walk the subtree and bump
mnt_busy on everything (by 1 + number of non-busy children).  Then drop
vfsmount_lock and do as usual, dropping references in tree being copied
as you go.  Nothing will get attached or detached due to namespace_sem,
nothing will get evicted by anybody other than you since you've got all
that stuff pinned down.  End of story...

  reply	other threads:[~2007-05-23 15:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22 18:48 [RFC PATCH] file as directory Miklos Szeredi
2007-05-22 22:10 ` Al Viro
2007-05-23  6:36   ` Miklos Szeredi
2007-05-23  7:03     ` Al Viro
2007-05-23  7:19       ` Miklos Szeredi
2007-05-23  7:36         ` Al Viro
2007-05-23  8:05           ` Miklos Szeredi
2007-05-23  8:29             ` Al Viro
2007-05-23  9:03               ` Miklos Szeredi
2007-05-23  9:58                 ` Al Viro
2007-05-23 10:14                   ` Miklos Szeredi
2007-05-23  9:16             ` Jan Blunck
2007-05-23  9:28               ` Miklos Szeredi
2007-05-23 12:34           ` Trond Myklebust
2007-05-23 12:40             ` Al Viro
2007-05-23  9:21     ` Jan Blunck
2007-05-23  9:35       ` Miklos Szeredi
2007-05-24 12:07     ` Pavel Machek
2007-05-28 14:43       ` Miklos Szeredi
2007-05-22 23:26 ` Shaya Potter
2007-05-23  6:39   ` Miklos Szeredi
2007-05-23  9:51 ` Al Viro
2007-05-23 10:09   ` Miklos Szeredi
2007-05-23 10:24     ` Miklos Szeredi
2007-05-23 10:24     ` Al Viro
2007-05-23 10:40       ` Miklos Szeredi
2007-05-23 11:39         ` Al Viro
2007-05-23 12:16           ` Al Viro
2007-05-23 13:01             ` Miklos Szeredi
2007-05-23 13:51               ` Al Viro
2007-05-23 14:32                 ` Miklos Szeredi
2007-05-23 15:06                   ` Al Viro [this message]
2007-05-23 15:25                     ` Miklos Szeredi
2007-05-23 15:37                       ` Al Viro
2007-05-23 15:55                         ` Miklos Szeredi
2007-05-23 13:23           ` Ph. Marek
2007-05-23 13:54             ` Al Viro
2007-05-23 12:01 ` Jan Engelhardt
2007-05-23 13:20 ` Jaroslav Sykora

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=20070523150602.GZ4095@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@linux-foundation.org \
    /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