From: Nathan Scott <nathans@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Matthew Wilcox <matthew@wil.cx>,
linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [LOCKDEP] xfs: possible recursive locking detected
Date: Wed, 5 Jul 2006 13:23:29 +1000 [thread overview]
Message-ID: <20060705132328.C1521039@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <20060704091247.GA15982@elte.hu>; from mingo@elte.hu on Tue, Jul 04, 2006 at 11:12:47AM +0200
On Tue, Jul 04, 2006 at 11:12:47AM +0200, Ingo Molnar wrote:
> * Nathan Scott <nathans@sgi.com> wrote:
> > That would be good, but it doesn't work for all situations
> > unfortunately, and it would loose that debug-kernel sanity checking
> > that we have in there which validates ilock/iolock ordering rules.
>
> do you have anything in there that spinlock/mutex debugging or lockdep
> does not catch? If yes then i'll add it to the generic lock debugging
> code.
The thing we're catching automatically there is potential ordering
violations on the XFS inode iolock vs ilock. I don't know if the
other methods can help us there too or not.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-07-05 3:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-04 0:41 [LOCKDEP] xfs: possible recursive locking detected Alexey Dobriyan
2006-07-04 1:18 ` Matthew Wilcox
2006-07-04 1:25 ` Nathan Scott
2006-07-04 6:32 ` Ingo Molnar
2006-07-04 6:56 ` Nathan Scott
2006-07-04 8:41 ` Ingo Molnar
2006-07-04 9:11 ` Nathan Scott
2006-07-04 9:12 ` Ingo Molnar
2006-07-05 3:23 ` Nathan Scott [this message]
2006-07-05 4:44 ` Arjan van de Ven
2006-07-04 9:57 ` Ingo Molnar
2006-07-04 13:03 ` Ingo Molnar
2006-07-05 5:26 ` Nathan Scott
2006-07-05 6:46 ` Ingo Molnar
2006-07-05 6:58 ` Nathan Scott
2006-07-05 3:37 ` Nathan Scott
[not found] ` <20060704191100.C1497438__38681.8935432986$1152004607$gmane$org@wobbly.melbourne.sgi.com>
2006-07-04 12:42 ` Andi Kleen
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=20060705132328.C1521039@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=adobriyan@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=xfs@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;
as well as URLs for NNTP newsgroup(s).