On Fri, Oct 08, 2010 at 04:21:31PM +1100, Dave Chinner wrote: > From: Dave Chinner <dchinner@xxxxxxxxxx> > > All the functionality that the inode_lock protected has now been > wrapped up in new independent locks and/or functionality. Hence the > inode_lock does not serve a purpose any longer and hence can now be > removed. > > Based on work originally done by Nick Piggin. I don't really agree with how this is structured, doing lock splitups and changes and things under the inode_lock and then lifting it here. If nothing else, than the practical implication that any locking problem in the patchset is going to bisect down to this patch. My approach of being ultra conservative in the initial breaking steps, then removing inode_lock, then implementing more aggressive locking and less trivial transforms IMO is the better way to go. It has worked very well for me doing both the inode and the dcache work, and it has made it easy to understand and debug. -- 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
