All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Sharp <andy@ccpu.com>
To: Florin Malita <mali@go.ro>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Mountpoint lookup
Date: Wed, 5 Feb 2003 11:13:00 -0800	[thread overview]
Message-ID: <20030205191300.GA16314@ccpu.com> (raw)
In-Reply-To: <1044457119.23738.131.camel@zed.malinux.net>

On Wed, Feb 05, 2003 at 05:02:01PM +0200, Florin Malita wrote:
> Is there a way of finding the mountpoint a fs is being mounted on at
> read_super time?
> 
> I'm developing a userland filesystem interface (LUFS -
> http://lufs.sourceforge.net) and the only way of getting the mountpoint
> I found so far is to wait until I get a struct file* (in readdir for
> example) and then go through its f_vfsmount, building the mountpoint
> path. This is race prone.
> 
> I suspect there's some sort of Zen restriction floating around the
> mountpoint (the darn fs shall not need to know its mountpoint) but I'm
> relying on it for absolute symlinks remapping.

It's the bizarre code of the FS, happy to give you your 'device' but
not your mount path.  It is, however, almost always in the data pointer.
Look at the source for the mount command, or write your own mount
command if that regular one isn't giving you what you want.  I recently
dealt with this exact issue, but I am using my own mount command so it
was no biggy.

a

  parent reply	other threads:[~2003-02-05 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 15:02 Mountpoint lookup Florin Malita
2003-02-05 15:03 ` Christoph Hellwig
     [not found]   ` <1044459408.23735.147.camel@zed.malinux.net>
     [not found]     ` <20030205154536.A21838@infradead.org>
2003-02-05 20:03       ` Florin Malita
2003-02-05 21:15         ` Bryan Henderson
2003-02-06 10:39           ` Florin Malita
2003-02-22 18:56             ` David Chow
2003-02-05 19:13 ` Andrew Sharp [this message]
2003-02-05 19:18   ` Christoph Hellwig
2003-02-05 20:06     ` Bryan Henderson

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=20030205191300.GA16314@ccpu.com \
    --to=andy@ccpu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mali@go.ro \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.