From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 03/17] fs: icache lock inode hash Date: Fri, 1 Oct 2010 02:06:50 -0400 Message-ID: <20101001060650.GH32349@infradead.org> References: <1285762729-17928-1-git-send-email-david@fromorbit.com> <1285762729-17928-4-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 Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:39096 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754033Ab0JAGGv (ORCPT ); Fri, 1 Oct 2010 02:06:51 -0400 Content-Disposition: inline In-Reply-To: <1285762729-17928-4-git-send-email-david@fromorbit.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Sep 29, 2010 at 10:18:35PM +1000, Dave Chinner wrote: > From: Nick Piggin > > Currently the inode hash lists are protected by the inode_lock. To > allow removal of the inode_lock, we need to protect the inode hash > table lists with a new lock. Nest the new inode_hash_lock inside the > inode_lock to protect the hash lists. There is no reason to make inode_hash_lock global, it's only used inside inode.c