On Thu, Feb 10, 2005 at 02:50:02PM +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... > > The igrab() effectively guarantees that iput() is called on all attr > inodes before clear_inode on the 'parent' can be invoked.
Yes, but why exactly is this important. It looks like you're absuing the refcount on the 'parent' inode for some shared data? - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
