On Mon, 2005-04-18 at 13:46 +0100, Christoph Hellwig wrote: > Any, this sounds like you'd want to use ilookup because you don't want > to read the inode in the cache anyway, right?
We use ilookup() in some circumstances -- if the inode has zero nlink and hence we definitely don't want to pull it back again if it's gone. But sometimes we really do mean to use iget() to bring it into core. And it's in that case that I believe Artem has found the problem, because if I understand correctly he's still seeing two consecutive calls to read_inode() for the same inode, without a clear_inode() in between. prune_icache() is removing the inode from i_hash at line 457 of inode.c, then being preempted when it drops the inode_lock at line 464, which is _before_ it calls dispose_list() to actually get rid of the inode(s) in question. So when iget() is called, the VFS ends up calling read_inode() again instead of waiting for the original inode to finish going away. -- dwmw2 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
