On Tue, Oct 19, 2010 at 12:36:55PM -0400, Eric Paris wrote: > I ask Al about reusing this field long ago and he indicated it had a > very different meaning. I can't remember what he indicated it meant off > the top of my head but I'll take a look at it again. > i_count, I believe, is much different. i_count is counting the number > of dentries in core referencing the inode, even if none of them are > being used in any struct file or if one dentry is being referenced in > 1000 struct files. The IMA counters are from a higher level, they > counts the number of struct files referencing this inode. a) i_writecount is about VM_DENYWRITE, basically. Reusing it for ima could get unpleasant; when it's positive, we are fine, but it can get negative as well. IMA will have interesting time dealing with that. b) i_count is simply a refcount for struct inode. Not exactly the number of dentries, but that's the main contributor. Basically, that's "how many pointers outside of inode hash chains point that that struct inode at the moment". -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
