[Top] [All Lists]

Re: -mm: xfs lockdep warning

To: Tejun Heo <tj@xxxxxxxxxx>
Subject: Re: -mm: xfs lockdep warning
From: Torsten Kaiser <just.for.lkml@xxxxxxxxxxxxxx>
Date: Tue, 5 Oct 2010 19:54:32 +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>
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mqQSTj2ivc09NYY+J0H3+qIgL8yGRrvQ1jORHPHSeqc=; b=pPS+nYfCVzcXDGOcEqPldQ2/oDF2ZRHXqOP0ewHpjtJ/ItjWONPMdXBh6Xw/pOQzmh /pGorDP/V459alp5V7s1xBYXP6zC1uSGLDRSEe62WVft86rZ5488VFwRCUjmozvvgSw1 NNF92WKt61DHL/DOI9RmiE38UA4WUafdLLFPM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wiM3GunVYEDo7zHgp4CdZDByuokZykR4JLaCudB0Ki6w8rgmtm/WgMvY74RTBUfDHZ TaTRw5mFuiitnEvBcM8Bj8KXGegyFajdiaPayptoVzM405MJSMyODETUKL/JcKHjGrSC sGHWJWdTnOeic5Pt2kidhYJYxOdn9c/47DOso=
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>
On Tue, Oct 5, 2010 at 6:51 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> Hello,
> This is getting confusing.
> 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?

Not 100%, but apart from the md/dm-worker the other prcesses got stuck
in sync_page() and do_lockup() and these function look filesystem
related. And the only filesystem I'm using on that system is XFS.

And having just read about some problems (that were fixed in
2.6.36-rc5) regarding XFS vs the new workqueues, I "feared" that I
somehow triggered some funny interaction between the workqueues of
XFS, md-raid1 and dm-crypt.

> Also, can you please enable frame pointers so that we can get more
> reliable backtrace?

I will do that and see if -rc6 gets stuck the same way.
But it might take until tomorrow to test this.

>> 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.
> Thanks.
> --
> tejun

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