From: Ram Pai <linuxram@us.ibm.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel@vger.kernel.org
Subject: Re: how to show propagation state for mounts
Date: Wed, 20 Feb 2008 11:42:28 -0800 [thread overview]
Message-ID: <1203536549.28525.24.camel@ram.us.ibm.com> (raw)
In-Reply-To: <20080220163102.GA27736@parisc-linux.org>
On Wed, 2008-02-20 at 09:31 -0700, Matthew Wilcox wrote:
> On Wed, Feb 20, 2008 at 04:04:22PM +0000, Al Viro wrote:
> > It's less about the form of representation (after all, we generate poll
> > events when contents of that sucker changes, so one *can* get a consistent
> > snapshot of the entire thing) and more about having it self-contained
> > when we have namespaces in the play.
> >
> > IOW, the data in there should give answers to questions that make sense.
> > "Do events get propagated from this vfsmount I have to that vfsmount I have?"
> > is a meaningful one; ditto for "are events here propagated to somewhere I
> > don't see?" or "are events getting propagated here from somewhere I don't
> > see?".
>
> Why do those last two questions deserve an answer? How will a person's
> or application's behaviour be affected by whether a change will
> propagate to something they don't know about and can't see?
Well, I do not want to be surprised to see a mount suddenly show up in
my namespace because of some action by some other user in some other
namespace. Its going to happen anyway if the namespace is forked of
a namespace that had shared mounts in them. However I would rather
prefer to know in advance the spots (mounts) where such surprises can
happen. Also I would prefer to know how my actions will effect mounts in
other namespaces.
RP
>
prev parent reply other threads:[~2008-02-20 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-20 15:39 how to show propagation state for mounts Miklos Szeredi
2008-02-20 16:04 ` Al Viro
2008-02-20 16:27 ` Miklos Szeredi
2008-02-20 19:29 ` Ram Pai
2008-02-20 21:14 ` Al Viro
2008-02-20 21:35 ` Miklos Szeredi
2008-02-22 14:46 ` [rfc patch] " Miklos Szeredi
2008-03-05 19:25 ` Serge E. Hallyn
2008-03-05 19:34 ` Miklos Szeredi
2008-03-05 20:23 ` Ram Pai
2008-03-10 6:53 ` [RFC PATCH v2] vfs: optimization to /proc/<pid>/mountinfo patch Ram Pai
2008-03-10 7:10 ` Christoph Hellwig
2008-03-10 11:39 ` Miklos Szeredi
2008-02-20 16:31 ` how to show propagation state for mounts Matthew Wilcox
2008-02-20 19:42 ` Ram Pai [this message]
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=1203536549.28525.24.camel@ram.us.ibm.com \
--to=linuxram@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.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: 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).