xfs-masters
[Top] [All Lists]

[xfs-masters] Re: [BUG] Lockdep warning with XFS on 2.6.22-rc6

To: "Johannes Weiner" <hannes-kernel@xxxxxxxxxxxx>
Subject: [xfs-masters] Re: [BUG] Lockdep warning with XFS on 2.6.22-rc6
From: "Satyam Sharma" <satyam.sharma@xxxxxxxxx>
Date: Mon, 25 Jun 2007 21:24:11 +0530
Cc: "Linux Kernel Mailing List" <linux-kernel@xxxxxxxxxxxxxxx>, xfs-masters@xxxxxxxxxxx, "David Chinner" <dgc@xxxxxxx>, "Ingo Molnar" <mingo@xxxxxxx>
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=CAw572aI3xySyTb1N93r/Iu1RYBZJiaLHNbjVOjLY2AGxDgN6H86E7TdhBfIOzwObX71AiHFR6uT2ZTimeC8gL/SEEzi+11CEAX9UqyWvQq4YF544E0bZ2dO9ADPuBo4oiH+1TBUK9qCSioJBxavzJCEEWGzutAOwfP6QwztuoU=
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=
In-reply-to: <20070625104956.GA22130@saeurebad.de>
References: <20070625104956.GA22130@saeurebad.de>
Reply-to: xfs-masters@xxxxxxxxxxx
Sender: xfs-masters-bounce@xxxxxxxxxxx
On 6/25/07, Johannes Weiner <hannes-kernel@xxxxxxxxxxxx> 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


<Prev in Thread] Current Thread [Next in Thread>