On Wed, 2 May 2001, Matthew Wilcox wrote: > > I never understood why you can't do it completely inode local protected > > by the inode lock; but then I don't claim that I understand fs/locks.c > > inode_lock claims it's for protecting the list manipulations, not for > protecting any element in an individual inode. Though in practice it > seems to be used for protecting i_state as well. I think I'd rather use For all practical purposes i_state goes together with i_list. > > Or just walk the inode hash ? Who the hell have said that filesystem has to insert its inodes into hash? The _only_ reason why hash exists is that many filesystems find iget() a useful helper function. It's by no means a fundamental object. - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED]
