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: <AANLkTinwFix7br+p+U2X_mNLTbb0umxQEL5+bhp5N0jW@mail.gmail.com>
Date:	Tue, 5 Oct 2010 19:54:32 +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:51 PM, Tejun Heo <tj@...nel.org> 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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/