Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756143AbXFYPyU (ORCPT ); Mon, 25 Jun 2007 11:54:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751920AbXFYPyN (ORCPT ); Mon, 25 Jun 2007 11:54:13 -0400 Received: from wr-out-0506.google.com ([64.233.184.235]:1348 "EHLO wr-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751574AbXFYPyM (ORCPT ); Mon, 25 Jun 2007 11:54:12 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aenfWrSJp/H3hdaCvldqzL3Kk/zh0v4BZ9R+IgIFeb9RAz6Si3P+ADEqViYpSedRp4WmE+GAD+XoqGraff8VZBs57Pm6NE9mUdbGtJqNGfwbyeE/7scl2vI0PI+ZgmvDbLuNfUaI/tbwBZWYUf0URn41Rn2qZPpmKbi3G97uAGU= Message-ID: Date: Mon, 25 Jun 2007 21:24:11 +0530 From: "Satyam Sharma" To: "Johannes Weiner" Subject: Re: [BUG] Lockdep warning with XFS on 2.6.22-rc6 Cc: "Linux Kernel Mailing List" , xfs-masters@oss.sgi.com, "David Chinner" , "Ingo Molnar" In-Reply-To: <20070625104956.GA22130@saeurebad.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070625104956.GA22130@saeurebad.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1068 Lines: 29 On 6/25/07, Johannes Weiner wrote: > [...] > this is what just hit the ring buffer when I was surfing with elinks on a > brand-new -rc6. Johannes: This is a known bogus warning. You can safely ignore it. David, Ingo: [ Ok, so we know that XFS wants to lock inodes in ascending inode number order and not strictly the parent-first-child-second order that rest of the fs/ code does, so that makes it difficult to teach lockdep about this kind of lock ordering ... ] However, this (bogus) warning still causes way too much noise on the lists (2-3 or more every week?) and most users wouldn't understand how or why this warning is bogus, so would get unnecessarily disturbed about it. Could there be a way to whitelist such "known bogus cases" in lockdep and stop it from complaining? Satyam - 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/