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:50:03 +0100 Message-ID: <20050210145003.GA7399@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> <20050210144254.GA7222@lst.de> <1108046906.12000.16.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]:34519 "EHLO mail.lst.de") by vger.kernel.org with ESMTP id S262122AbVBJOuM (ORCPT ); Thu, 10 Feb 2005 09:50:12 -0500 To: Anton Altaparmakov Content-Disposition: inline In-Reply-To: <1108046906.12000.16.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:48:26PM +0000, Anton Altaparmakov wrote: > If the igrab() were not done, it would be possible for clear_inode to be > called on the 'parent' inode whilst at the same time one or more attr > inodes (belonging to this 'parent') are in use and Bad Things(TM) would > happen... What bad thing specificly? If there's shared information we should probably refcount them separately.