On Thu, Sep 19, 2013 at 09:26:49AM +0100, David Howells wrote: > There's a potential race between evict_inode() and iget5_locked() in which the > former can be tearing down an inode corresponding to a file whilst the latter > is trying to set up a new inode corresponding to that same file - but it's > possible that the cleanups for the former may adversely affect the setups for > the latter. evict() calls ->evict_inode() before removing it from hash. It's called only with I_FREEING already set. If find_inode() runs across that sucker, it will wait for evict() to do wake_up_bit(&inode->i_state, __I_NEW); (after return from ->evict_inode() and after removal from hash chain) and repeat the search. Details, please... -- 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
