From: Christoph Hellwig <hch@infradead.org>
To: Andrew Sharp <andy@ccpu.com>
Cc: Florin Malita <mali@go.ro>, linux-fsdevel@vger.kernel.org
Subject: Re: Mountpoint lookup
Date: Wed, 5 Feb 2003 19:18:33 +0000 [thread overview]
Message-ID: <20030205191833.A25400@infradead.org> (raw)
In-Reply-To: <20030205191300.GA16314@ccpu.com>; from andy@ccpu.com on Wed, Feb 05, 2003 at 11:13:00AM -0800
On Wed, Feb 05, 2003 at 11:13:00AM -0800, Andrew Sharp wrote:
> 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.
Unfortunately the second mount of the same device won't even call back into
your filesystem code. Or mount --move or mount --bind. Youre hack is
just broken, there is no non-ambiguous mount path -> superblock mapping
in linux.
next prev parent reply other threads:[~2003-02-05 19:18 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
2003-02-05 19:18 ` Christoph Hellwig [this message]
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=20030205191833.A25400@infradead.org \
--to=hch@infradead.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox