From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752568Ab0JPQ7c (ORCPT ); Sat, 16 Oct 2010 12:59:32 -0400 Received: from canuck.infradead.org ([134.117.69.58]:34548 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751430Ab0JPQ7b (ORCPT ); Sat, 16 Oct 2010 12:59:31 -0400 Date: Sat, 16 Oct 2010 12:59:30 -0400 From: Christoph Hellwig To: Nick Piggin Cc: Dave Chinner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 04/19] fs: Implement lazy LRU updates for inodes. Message-ID: <20101016165930.GA20626@infradead.org> References: <1287216853-17634-1-git-send-email-david@fromorbit.com> <1287216853-17634-5-git-send-email-david@fromorbit.com> <20101016092916.GA32197@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101016092916.GA32197@amd> User-Agent: Mutt/1.5.20 (2009-08-17) X-SRS-Rewrite: SMTP reverse-path rewritten from by canuck.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 16, 2010 at 08:29:16PM +1100, Nick Piggin wrote: > On Sat, Oct 16, 2010 at 07:13:58PM +1100, Dave Chinner wrote: > > @@ -502,11 +527,15 @@ static void prune_icache(int nr_to_scan) > > iput(inode); > > spin_lock(&inode_lock); > > > > - if (inode != list_entry(inode_unused.next, > > - struct inode, i_list)) > > - continue; /* wrong inode or list_empty */ > > - if (!can_unuse(inode)) > > + /* > > + * if we can't reclaim this inode immediately, give it > > + * another pass through the free list so we don't spin > > + * on it. > > + */ > > + if (!can_unuse(inode)) { > > + list_move(&inode->i_list, &inode_unused); > > continue; > > + } > > } > > list_move(&inode->i_list, &freeable); > > WARN_ON(inode->i_state & I_NEW); > > This is a bug, actually 2 bugs, which is why I omitted it in the version > you picked up. I agree we want the optimisation though, so I've added it > back in my tree. > > After you iput() and then re take the inode lock, you can't reference > the inode because you don't know what happened to it. You need to keep > that pointer check to verify it is still there. I don't think the pointer check will work either. By the time we retake the lru lock the inode might already have been reaped through a call to invalidate_inodes. There's no way we can do anything with it after iput. What we could do is using variant of can_unuse to decide to move the inode to the front of the lru before doing the iput. That way we'll get to it next after retaking the lru lock if it's still there.