From: Tejun Heo <tj@kernel.org>
To: Torsten Kaiser <just.for.lkml@googlemail.com>
Cc: Yang Ruirui <ruirui.r.yang@tieto.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
Christoph Hellwig <hch@infradead.org>,
Alex Elder <aelder@sgi.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: -mm: xfs lockdep warning
Date: Tue, 05 Oct 2010 18:51:05 +0200 [thread overview]
Message-ID: <4CAB5779.5020901@kernel.org> (raw)
In-Reply-To: <AANLkTi=3jjoCtYoK0endt8OM=omygO284WN2ZQZ=jceo@mail.gmail.com>
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?
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.
Thanks.
--
tejun
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-05 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 7:46 -mm: xfs lockdep warning 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 [this message]
2010-10-05 16:55 ` Tejun Heo
2010-10-05 18:09 ` Torsten Kaiser
2010-10-05 18:17 ` Christoph Hellwig
2010-10-05 17:54 ` Torsten Kaiser
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=4CAB5779.5020901@kernel.org \
--to=tj@kernel.org \
--cc=aelder@sgi.com \
--cc=akpm@linux-foundation.org \
--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