On Wed, Sep 29, 2010 at 10:18:40PM +1000, Dave Chinner wrote: > From: Nick Piggin <npiggin@xxxxxxx> > > Before removing the inode_lock, we need to protect the inode list > operations with the inode->i_lock. This ensures that all inode state > changes are serialised regardless of the fact that the lists they > are moving around might be protected by different locks. Hence we > can safely protect an inode in transit from one list to another > without needing to hold all the list locks at the same time. The subject does not seem to match the patch description and content. -- 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
