From: Tejun Heo <tj@kernel.org>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Yang Ruirui <ruirui.r.yang@tieto.com>,
Andrew Morton <akpm@linux-foundation.org>,
xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
Alex Elder <aelder@sgi.com>
Subject: Re: -mm: xfs lockdep warning
Date: Tue, 05 Oct 2010 18:55:16 +0200 [thread overview]
Message-ID: <4CAB5874.9060106@kernel.org> (raw)
In-Reply-To: <4CAB5779.5020901@kernel.org>
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
lockup?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-10-05 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 7:46 Yang Ruirui
2010-09-17 0:52 ` Dave Chinner
2010-09-20 19:13 ` Christoph Hellwig
2010-09-25 13:08 ` Torsten Kaiser
2010-10-04 9:01 ` Tejun Heo
2010-10-04 9:21 ` Dave Chinner
2010-10-05 10:09 ` Torsten Kaiser
2010-10-05 16:51 ` Tejun Heo
2010-10-05 16:55 ` Tejun Heo [this message]
2010-10-05 18:09 ` Torsten Kaiser
2010-10-05 18:17 ` Christoph Hellwig
2010-10-05 17:54 ` Torsten Kaiser
[not found] ` <AANLkTineNfy+hfnK-sjHNB+h05oC4qbJ+81pg95Bmn=b@mail.gmail.com>
[not found] ` <4CAC366E.7070609@kernel.org>
[not found] ` <4CAC38D9.8020407@kernel.org>
[not found] ` <AANLkTikw=ObzgWu35fsuriC-jVrzDRHRfFJeT8-4-ndY@mail.gmail.com>
[not found] ` <4CAC934E.2030807@kernel.org>
[not found] ` <AANLkTinrBeMDyQJaYJFALTPpOgEaAy7yoPdyQ0Gpay3G@mail.gmail.com>
[not found] ` <4CACC0CD.5000001@kernel.org>
2010-10-07 11:14 ` Tejun Heo
2010-10-07 13:21 ` Torsten Kaiser
2010-10-07 14:05 ` Tejun Heo
2010-10-07 15:15 ` Torsten Kaiser
2010-10-07 15:41 ` Tejun Heo
[not found] ` <AANLkTi=LnbH7LNUr+YuR+uKLFasKyV7hOZc1zD0qqHnW@mail.gmail.com>
2010-10-08 12:40 ` Tejun Heo
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=4CAB5874.9060106@kernel.org \
--to=tj@kernel.org \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ruirui.r.yang@tieto.com \
--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
Powered by JetHome