From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: d_path and stackable filesystems Date: 29 Jul 2003 00:02:25 -0400 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <1059451345.911.29.camel@zaphod> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:32176 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S271106AbTG2ECn (ORCPT ); Tue, 29 Jul 2003 00:02:43 -0400 Received: from [192.168.0.103] (user-0cces8t.cable.mindspring.com [24.199.113.29]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.9/8.12.9) with ESMTP id h6T42fTx004202 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 29 Jul 2003 00:02:42 -0400 (EDT) To: linux-fsdevel@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org I'm trying to use d_path() inside a stackable filesystems (using fist), but it only figures out the path until the mount point of the stackable fs. Is this a limitation of the d_path algorithm, fist, both? any way of me working around it? as far as I can tell it's because of this piece of code if (dentry == vfsmnt->mnt_root || IS_ROOT(dentry) ) { /* Global root? */ if (vfsmnt->mnt_parent == vfsmnt) goto global_root; namely the vfsmnt->mnt_parent == vfsmnt. any ideas on how I can work around it? thanks, shaya