From: Christoph Hellwig Subject: Re: Mountpoint lookup Date: Wed, 5 Feb 2003 19:18:33 +0000 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20030205191833.A25400@infradead.org> References: <1044457119.23738.131.camel@zed.malinux.net> <20030205191300.GA16314@ccpu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florin Malita , linux-fsdevel@vger.kernel.org Return-path: To: Andrew Sharp Content-Disposition: inline In-Reply-To: <20030205191300.GA16314@ccpu.com>; from andy@ccpu.com on Wed, Feb 05, 2003 at 11:13:00AM -0800 List-Id: linux-fsdevel.vger.kernel.org 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.