[Top] [All Lists]

Re: -mm: xfs lockdep warning

To: Torsten Kaiser <just.for.lkml@xxxxxxxxxxxxxx>
Subject: Re: -mm: xfs lockdep warning
From: Tejun Heo <tj@xxxxxxxxxx>
Date: Tue, 05 Oct 2010 18:55:16 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Yang Ruirui <ruirui.r.yang@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Alex Elder <aelder@xxxxxxx>
In-reply-to: <4CAB5779.5020901@xxxxxxxxxx>
References: <201009161546.16909.ruirui.r.yang@xxxxxxxxx> <20100917005227.GJ24409@dastard> <20100920191355.GA28443@xxxxxxxxxxxxx> <AANLkTi=45J+=ytj=NC4bYTVJFRakNQQiFd35K7mrf+Gq@xxxxxxxxxxxxxx> <4CA997DF.5030008@xxxxxxxxxx> <20101004092107.GJ4681@dastard> <AANLkTi=3jjoCtYoK0endt8OM=omygO284WN2ZQZ=jceo@xxxxxxxxxxxxxx> <4CAB5779.5020901@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
On 10/05/2010 06:51 PM, Tejun Heo wrote:
> On 10/05/2010 12:09 PM, Torsten Kaiser wrote:
>> 2) the hang with 2.6.35-rc5 I have seen twice (triggered probably by
>> high load while building KOffice on an tmpfs)
> The trace doesn't seem to firmly point at xfs locking up.  There are
> md and dm crypt involved.  Are you sure this is locking up inside xfs?
> Also, can you please enable frame pointers so that we can get more
> reliable backtrace?
>> 3) the lockdep issue that started this thread and that I am seeing in
>> mainline 2.6.36-rc5 and -rc6 and that seems to be rather easy to
>> trigger for me.
>> Because 3) is regarded as a false positive, it should not be the cause
>> of 2)
> For now, let's not draw any conclusion or mix the issues.  I'll look
> up the original thread and look into what the lockdep warning means.

Ah, okay, David already looked into it and concluded it to be a
spurious one.  Can you please attach full kernel message of the



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