From: Christoph Hellwig Subject: Re: [PATCH 10/18] fs: Factor inode hash operations into functions Date: Fri, 8 Oct 2010 03:29:47 -0400 Message-ID: <20101008072947.GC7831@lst.de> References: <1286515292-15882-1-git-send-email-david@fromorbit.com> <1286515292-15882-11-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 canuck.infradead.org ([134.117.69.58]:51697 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753157Ab0JHH3s (ORCPT ); Fri, 8 Oct 2010 03:29:48 -0400 Content-Disposition: inline In-Reply-To: <1286515292-15882-11-git-send-email-david@fromorbit.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Oct 08, 2010 at 04:21:24PM +1100, Dave Chinner wrote: > From: Dave Chinner > > Before replacing the inode hash locking with a more scalable > mechanism, factor the removal of the inode from the hashes rather > than open coding it in several places. > > Based on a patch originally from Nick Piggin. Looks good as an equal transformation, but what code is doing with remove_inode_hash looks really buggy. It's doing a re-hash of a live inode which is probably causing enough problems by itself, but should at least have locks for it. Anyway, that's something for the coda folks to sort out. Reviewed-by: Christoph Hellwig