linux-kernel - Re: -mm: xfs lockdep warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTikzvD6B=8bGp6h2+bjV5BimErqLOgt2Ujsn053C@mail.gmail.com>
Date:	Tue, 5 Oct 2010 20:09:58 +0200
From:	Torsten Kaiser <just.for.lkml@...glemail.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Dave Chinner <david@...morbit.com>,
	Christoph Hellwig <hch@...radead.org>,
	Yang Ruirui <ruirui.r.yang@...to.com>,
	Andrew Morton <akpm@...ux-foundation.org>, xfs@....sgi.com,
	linux-kernel@...r.kernel.org, Alex Elder <aelder@....com>
Subject: Re: -mm: xfs lockdep warning

On Tue, Oct 5, 2010 at 6:55 PM, Tejun Heo <tj@...nel.org> wrote:
> 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?

Here is the complete log from bootup until the hang happened the second time.
I just logged into KDE and then started the upgrade of KOffice, which
meant that the package manager started to compile 4 programs each with
-j5. After a few minutes the load got to ~18 and probably at the point
where filecache and GCCs filled up my 4GB RAM the system got stuck.
The mouse so longer moved and SysRq+S did not work. The log was
captured via serial console on a second system.

I will try tomorrow with frame pointers enabled...

Torsten

View attachment "xfs-lockup.txt" of type "text/plain" (71116 bytes)