From: Mathieu Dube <mathieu.dube@nexsan.ca>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: mountpoint information a get_sb
Date: Thu, 23 Nov 2006 13:51:24 +0000 [thread overview]
Message-ID: <1164289884.15003.13.camel@mdube> (raw)
In-Reply-To: <20061123183227.GL3078@ftp.linux.org.uk>
On Thu, 2006-11-23 at 18:32 +0000, Al Viro wrote:
> It might be mounted at any number of places, including 0. Moreover,
> it might be mounted at some place only to be immediately moved
> elsewhere.
>
> The question makes no sense.
Im sorry Im fairly new to this.
youre saying there is no way to know the mount point unless its already
mounted?
for instance in kernel 2.2 you had a d_covers pointer to the dentry the
mount would be placed on?
I need to know the subtree that will be made invisible once the fs is
mounted
is there a way ?
-M
next prev parent reply other threads:[~2006-11-23 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 12:07 mountpoint information a get_sb Mathieu Dube
2006-11-23 18:32 ` Al Viro
2006-11-23 13:51 ` Mathieu Dube [this message]
2006-11-23 18:53 ` Matthew Wilcox
2006-11-23 19:46 ` Al Viro
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=1164289884.15003.13.camel@mdube \
--to=mathieu.dube@nexsan.ca \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ftp.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).