From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755820AbYIQSdl (ORCPT ); Wed, 17 Sep 2008 14:33:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754938AbYIQSda (ORCPT ); Wed, 17 Sep 2008 14:33:30 -0400 Received: from yx-out-2324.google.com ([74.125.44.29]:46622 "EHLO yx-out-2324.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754824AbYIQSd3 (ORCPT ); Wed, 17 Sep 2008 14:33:29 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=LCTMEKlDfncwZ7fTIRKqmNn85LJYFJJ3ecnhdfWXj3WBFyHQgxh8HfJiNNk3BHBkYB LdcSil291yPaBzK/QyZunVTojDIVSgo13ELgFdlFASZ6y6w1zy0n4ZhcelvaIYgW70jb QZVrjtV8TdQ9j4rt4b0QNpgk1Y2KX+gI/GAOU= Message-ID: Date: Wed, 17 Sep 2008 22:33:28 +0400 From: "Alexander Beregalov" To: "Alexander Beregalov" , rjw@sisk.pl, linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: 2.6.27-rc6: lockdep warning: iprune_mutex at shrink_icache_memory+0x38/0x1a8 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080913233138.GA19576@orion> <20080916025204.GL5811@disturbed> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2008/9/16 Alexander Beregalov : > 2008/9/16 Dave Chinner : >> On Sun, Sep 14, 2008 at 03:31:38AM +0400, Alexander Beregalov wrote: >>> Hi >>> >>> [ INFO: possible circular locking dependency detected ] >>> 2.6.27-rc6-00034-gd1c6d2e #3 >>> ------------------------------------------------------- >>> nfsd/1766 is trying to acquire lock: >>> (iprune_mutex){--..}, at: [] shrink_icache_memory+0x38/0x1a8 >>> >>> but task is already holding lock: >>> (&(&ip->i_iolock)->mr_lock){----}, at: [] >>> xfs_ilock+0xa2/0xd6 >>> >>> >>> I read files through nfs and saw delay for few seconds. >>> System is x86_32, nfs, xfs. >>> The last working kernel is 2.6.27-rc5, >>> I do not know yet is it reproducible or not. >> >> >> >> We need a FAQ for this one. It's a false positive. Google for an >> explanation - I've explained it 4 or 5 times in the past year and >> asked that the lockdep folk invent a special annotation for the >> iprune_mutex (or memory reclaim) because of the way it can cause >> recursion into the filesystem and hence invert lock orders without >> causing deadlocks..... > > Hi Dave > > Yes, you already explained a similar message to me, but it was a bug, > not false positive. > http://lkml.org/lkml/2008/7/3/29 > http://lkml.org/lkml/2008/7/3/315 > > I will try to bisect. > It is not a OOM case. > I can not reproduce it.