From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 11/18] fs: Introduce per-bucket inode hash locks Date: Fri, 8 Oct 2010 05:51:26 -0400 Message-ID: <20101008095126.GA15567@infradead.org> References: <1286515292-15882-1-git-send-email-david@fromorbit.com> <1286515292-15882-12-git-send-email-david@fromorbit.com> <20101008094915.GZ19804@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Al Viro Return-path: Received: from canuck.infradead.org ([134.117.69.58]:47300 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756776Ab0JHJvb (ORCPT ); Fri, 8 Oct 2010 05:51:31 -0400 Content-Disposition: inline In-Reply-To: <20101008094915.GZ19804@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Oct 08, 2010 at 10:49:15AM +0100, Al Viro wrote: > > HFS_I(inode)->rsrc_inode = dir; > > HFS_I(dir)->rsrc_inode = inode; > > igrab(dir); > > - hlist_add_head(&inode->i_hash, &HFS_SB(dir->i_sb)->rsrc_inodes); > > + hlist_bl_add_head(&inode->i_hash, &HFS_SB(dir->i_sb)->rsrc_inodes); > > mark_inode_dirty(inode); > > Lovely. What protects that list? Same question for hfsplus... Nothing. It's also never actually read. For hfsplus all that is fixed in my hfsplus tree, but I'll still need to find a sucker to backport all this to hfs.