From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 12/18] fs: add a per-superblock lock for the inode list
Date: Fri, 8 Oct 2010 03:35:33 -0400
Message-ID: <20101008073533.GA24089@infradead.org>
References: <1286515292-15882-1-git-send-email-david@fromorbit.com>
 <1286515292-15882-13-git-send-email-david@fromorbit.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
To: Dave Chinner <david@fromorbit.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <1286515292-15882-13-git-send-email-david@fromorbit.com>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On Fri, Oct 08, 2010 at 04:21:26PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
> 
> To allow removal of the inode_lock, we first need to protect the
> superblock inode list with its own lock instead of using the
> inode_lock. Add a lock to the superblock to protect this list and
> nest the new lock inside the inode_lock around the list operations
> it needs to protect.
> 
> Based on a patch originally from Nick Piggin.

Looks good,


Reviewed-by: Christoph Hellwig <hch@lst.de>