On Wed, Sep 29, 2010 at 10:18:34PM +1000, Dave Chinner wrote: > From: Nick Piggin <npiggin@xxxxxxx> > > To allow removal of the inode_lock, we first need to protect the > superblock inode list with it's own lock instead of using the > inode_lock for this purpose. Nest the new sb_inode_list_lock inside > the inode_lock around the list operations it needs to protect. Is there any good reason not to make this lock per-superblock? -- 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
