From: Eric Sandeen <sandeen@sandeen.net>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Lock debugging noise or real problem?
Date: Mon, 11 Aug 2008 21:48:28 -0500 [thread overview]
Message-ID: <48A0F9FC.1070805@sandeen.net> (raw)
In-Reply-To: <48A0F686.2090700@tlinx.org>
Linda Walsh wrote:
> Eric Sandeen wrote:
>> the explanation for xfs_fsr, at least, is the same as the last time you
>> brought it up ;)
>> http://lkml.org/lkml/2008/2/12/86
>> -Eric
>>
> ---
> Ah...Looks like the 1st xfs_fsr prob is the same as the one 6 months
> ago...(sorry)
> xfs_ilock & xfs_ilock
>
> But... the 3 imapds and the sort process were all 4 holding
> xfs_ilock & shrink_icache_memory
>
> And the other two xfs_fsr's were holding different locks than the
> 6-month-ago bug:
> dio_get_page & xfs_ilock
> Are these the same as well?
>
> I.e. looks like 3 possibly different probs:
> #1 (same as 6 months ago)...
> #2 (3)imapds & sort: holding xfs_ilock & shrink_icache
> #3 xfs_fsr with two different locks: dio_get_page & xfs_ilock>
http://www.google.com/search?q=xfs_fsr+dio_get_page+lockdep
-> http://oss.sgi.com/archives/xfs/2008-01/msg00042.html
I haven't looked closely at #2 but there have been so many lockdep
reports for xfs, and so many explanations of why they don't always get
along, you'll probably be able to find something with some searching.
-Eric
next prev parent reply other threads:[~2008-08-12 2:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 19:31 Lock debugging noise or real problem? Linda Walsh
2008-08-11 20:10 ` Eric Sandeen
2008-08-12 2:33 ` Linda Walsh
2008-08-12 2:48 ` Eric Sandeen [this message]
2008-08-12 3:35 ` Linda Walsh
2008-08-12 22:28 ` XFS " Linda A. Walsh
2008-08-13 0:58 ` Dave Chinner
2008-08-13 22:05 ` Linda Walsh
2008-08-14 0:41 ` Dave Chinner
2008-08-14 1:04 ` Linda Walsh
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=48A0F9FC.1070805@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--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