From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: linux-next: manual merge of the akpm tree with Linus' tree Date: Fri, 13 Sep 2013 16:31:38 -0400 Message-ID: References: <20130910222924.GB13318@ZenIV.linux.org.uk> <20130910153520.14e49cd32feb16d45eb8abac@linux-foundation.org> <20130910223624.GC13318@ZenIV.linux.org.uk> <20130910154116.cc4afe048213a779040ea3cc@linux-foundation.org> <20130910224823.GE13318@ZenIV.linux.org.uk> <20130910225934.GF13318@ZenIV.linux.org.uk> <20130913200000.GT13318@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-vb0-f43.google.com ([209.85.212.43]:65261 "EHLO mail-vb0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754287Ab3IMUbj (ORCPT ); Fri, 13 Sep 2013 16:31:39 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Al Viro Cc: Andrew Morton , Stephen Rothwell , linux-next , Linux Kernel Mailing List , Dave Chinner , Glauber Costa On Fri, Sep 13, 2013 at 4:25 PM, Linus Torvalds wrote: > > Yes. And I found the opposite bug in one place: when we are collecting > dentries by walking the parents etc, we do *not* hold the global RCU > lock, so we cannot use the "d_lru_shrink_list()" thing after all. It's > correct as far as the internal logic of fs/dcache.c goes, but it > violates the global LRU list rules. So I replaced that with a > dentry_lru_del() followed by a d_shrink_add() instead. Actually, I replaced it with d_lru_del()+d_shrink_add(), because afaik we should be guaranteed that the dentry in question is on the global RCU list (we checked that refcount is 0, and it's not on a local list). Agreed? The patch I sent out already had that version, I just "documented" my first one. Linus