mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Satyam Sharma" <satyam.sharma@gmail.com>
To: "Johannes Weiner" <hannes-kernel@saeurebad.de>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	xfs-masters@oss.sgi.com, "David Chinner" <dgc@sgi.com>,
	"Ingo Molnar" <mingo@elte.hu>
Subject: Re: [BUG] Lockdep warning with XFS on 2.6.22-rc6
Date: Mon, 25 Jun 2007 21:24:11 +0530	[thread overview]
Message-ID: <a781481a0706250854p4dad0cb6k20111db0f1c13e55@mail.gmail.com> (raw)
In-Reply-To: <20070625104956.GA22130@saeurebad.de>

On 6/25/07, Johannes Weiner <hannes-kernel@saeurebad.de> 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

  reply	other threads:[~2007-06-25 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 10:49 Johannes Weiner
2007-06-25 15:54 ` Satyam Sharma [this message]
2007-06-25 21:01   ` Ingo Molnar
2007-06-26  2:16     ` David Chinner
2007-06-26  9:35       ` Jarek Poplawski
2007-06-26 12:50         ` David Chinner
2007-06-27  6:42           ` [xfs-masters] " Tim Shimmin
2007-06-27 14:01           ` Thomas Sattler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a781481a0706250854p4dad0cb6k20111db0f1c13e55@mail.gmail.com \
    --to=satyam.sharma@gmail.com \
    --cc=dgc@sgi.com \
    --cc=hannes-kernel@saeurebad.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=xfs-masters@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®