linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ion Badulescu <ionut@badula.org>
Cc: "Charles P. Wright" <cpwright@cpwright.com>,
	linux-fsdevel@vger.kernel.org, ezk@cs.sunysb.edu
Subject: Re: Sick VFS question
Date: Tue, 25 Feb 2003 13:55:18 -0800	[thread overview]
Message-ID: <3E5BE646.80507@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0302251536370.32233-100000@guppy.limebrokerage.com>

Ion Badulescu wrote:
> 
> Direct mounts would solve all these issues in a much more elegant way. We 
> already have overlay mounts, we already have bind mounts, all the elements 
> are in place to support direct mounts without much effort.
> 
Yes, except for atomicity concerns.  Anyway, I had a talk with Linus
about this about an hour ago, and he suggested adding a notification
mechanism to the namespace (mount) mechanism and do things at that
level.  It entails more kernel core hacking, but it would be cleaner in
a whole lot of ways.  I will look into it this evening.

	-hpa



  parent reply	other threads:[~2003-02-25 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  9:48 Sick VFS question H. Peter Anvin
2003-02-25 16:19 ` Ion Badulescu
2003-02-25 17:30   ` Charles P. Wright
2003-02-25 17:57     ` H. Peter Anvin
2003-02-25 18:46     ` Ion Badulescu
2003-02-25 19:53       ` H. Peter Anvin
2003-02-25 20:39         ` Ion Badulescu
2003-02-25 21:06           ` Ion Badulescu
2003-02-25 21:55           ` H. Peter Anvin [this message]
2003-02-26 15:37             ` Erez Zadok
2003-02-26 15:45               ` H. Peter Anvin
2003-03-06 16:53       ` David Chow
2003-03-06 17:18         ` Charles P. Wright

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=3E5BE646.80507@zytor.com \
    --to=hpa@zytor.com \
    --cc=cpwright@cpwright.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=ionut@badula.org \
    --cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).