linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Mathieu Dube <mathieu.dube@nexsan.ca>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: mountpoint information a get_sb
Date: Thu, 23 Nov 2006 19:46:57 +0000	[thread overview]
Message-ID: <20061123194657.GM3078@ftp.linux.org.uk> (raw)
In-Reply-To: <1164289884.15003.13.camel@mdube>

On Thu, Nov 23, 2006 at 01:51:24PM +0000, Mathieu Dube wrote:
> 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?

I am saying that it can be mounted in any number of places at the same
time.
 
> for instance in kernel 2.2 you had a d_covers pointer to the dentry the
> mount would be placed on?

Kept in struct vfsmount since 2.4 and there can be many of those for the
same superblock.

> I need to know the subtree that will be made invisible once the fs is
> mounted

If you rely on something becoming invisible - you've got a problem.
It might be mounted elsewhere and not obscured there by anything.

If you want pass it *some* subtree, just pass it explicitly in the
options, but be ready to have it changed later on (stuff might be
mounted there, unmounted, moved around, etc.)

More details of what you are trying to do would be useful...

      parent reply	other threads:[~2006-11-23 19:46 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
2006-11-23 18:53     ` Matthew Wilcox
2006-11-23 19:46     ` Al Viro [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=20061123194657.GM3078@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mathieu.dube@nexsan.ca \
    /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).