From: Ram Pai <linuxram@us.ibm.com>
To: linux-fsdevel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, viro@parcelfarce.linux.theplanet.co.uk
Subject: shared subtree query
Date: Wed, 31 Aug 2005 17:00:09 -0700 [thread overview]
Message-ID: <1125532808.10823.105.camel@localhost> (raw)
Ok. I have shared subtree patches getting ready for review. I have
totally revamped the code from what I had sent last time, incorporating
all valuable comments Miklos had made. Offcourse I am yet to finish a
document that Andrew Morton had requested.
The patch snapshot at:
http://www.sudhaa.com/~ram/readahead/sharedsubtree
and the latest set of working patches are at:
http://www.sudhaa.com/~ram/readahead/sharedsubtree/shared.0831.1
Before I formally send the patches for a review, I have bumped into a
small issue, and I am not sure about the behavior.
Al Viro's RFC at http://lwn.net/Articles/119232/ says
5. umount
unmount everything that gets propagation from victim
Its hard to interpret what victim means. There can be two
interpretations to this.
1) the mount that got unmounted
2) the mount whose child got unmounted
I think its natural to assume (2), but (1) also makes sense sometimes.
Can somebody shed some light on this? Al Viro: please?
Thanks for your help,
RP
reply other threads:[~2005-09-01 0:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1125532808.10823.105.camel@localhost \
--to=linuxram@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.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).