From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: fishy ->put_inode usage in ntfs Date: Thu, 10 Feb 2005 15:42:54 +0100 Message-ID: <20050210144254.GA7222@lst.de> References: <20041014112607.GA24508@lst.de> <1097757569.21275.40.camel@imp.csi.cam.ac.uk> <20041014125933.GA26021@lst.de> <1097760404.21275.52.camel@imp.csi.cam.ac.uk> <20050210104719.GA2771@lst.de> <1108046439.12000.9.camel@imp.csi.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ntfs-dev , fsdevel Received: from verein.lst.de ([213.95.11.210]:24023 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S262124AbVBJOnE (ORCPT ); Thu, 10 Feb 2005 09:43:04 -0500 To: Anton Altaparmakov Content-Disposition: inline In-Reply-To: <1108046439.12000.9.camel@imp.csi.cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, Feb 10, 2005 at 02:40:39PM +0000, Anton Altaparmakov wrote: > I am not sure what you mean. The VFS layer does reference counting on > inodes. I have no choice in the matter. > > > Can someone ever grab a reference separate from it's master inode? > > Again, not sure what you mean. Could you elaborate? ntfs_read_locked_attr_inode() does igrab on the 'parent' inode currently. What do you need this for exactly - the attr inode goes away anyway when clear_inode is called on that 'parent' inode (in my scheme).