Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751197AbbGaSmY (ORCPT ); Fri, 31 Jul 2015 14:42:24 -0400 Received: from mail-io0-f170.google.com ([209.85.223.170]:34991 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750877AbbGaSmX (ORCPT ); Fri, 31 Jul 2015 14:42:23 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Fri, 31 Jul 2015 11:42:22 -0700 X-Google-Sender-Auth: wbZzvZOzTqOmeZux0zGhyYsXe5w Message-ID: Subject: Re: v4.2-rc dcache regression, probably 75a6f82a0d10 From: Linus Torvalds To: Hugh Dickins Cc: Al Viro , Linux Kernel Mailing List , linux-fsdevel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 24 On Fri, Jul 31, 2015 at 10:46 AM, Hugh Dickins wrote: > > Sounds like a dcache problem, and 75a6f82a0d10 seemed the only > likely candidate, so I experimented with reverting it yesterday, > and ran successfully for 24 hours. Hmm. Sounds odd. Are you running nfsd? That would explain why it happens on ext4 but not tmpfs: ext4 has a get_parent method that can get a disconnected entry, while tmpfs does not. That said, your load doesn't sound like it would actually ever trigger this, unless you just didn't mention that you also end up using that filesystem over nfs on another machine. So leave it running a while longer, but maybe it's 4bf46a272647 like Dominique suspects. Although I don't see how that could trigger anything either.. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/