Message-ID: <48A0F9FC.1070805@sandeen.net>
Date: Mon, 11 Aug 2008 21:48:28 -0500
From: Eric Sandeen <sandeen@sandeen.net>
User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707)
MIME-Version: 1.0
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?
References: <48A093A7.40606@tlinx.org> <48A09CA9.9080705@sandeen.net> <48A0F686.2090700@tlinx.org>
In-Reply-To: <48A0F686.2090700@tlinx.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1393
Lines: 40

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
--
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/