linux-kernel - Re: [2.6.20] BUG: workqueue leaked lock

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: <20070316144921.GB5877@ff.dom.local>
Date:	Fri, 16 Mar 2007 15:49:22 +0100
From:	Jarek Poplawski <jarkao2@...pl>
To:	Folkert van Heusden <folkert@...heusden.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...sign.ru>,
	Neil Brown <neilb@...e.de>
Subject: Re: [2.6.20] BUG: workqueue leaked lock

On 15-03-2007 20:17, Folkert van Heusden wrote:
>>> On Tue, 13 Mar 2007 17:50:14 +0100 Folkert van Heusden <folkert@...heusden.com> wrote:
>>> ...
>>> [ 1756.728209] BUG: workqueue leaked lock or atomic: nfsd4/0x00000000/3577
> ...
>>> [ 1846.684023]  [<c1003bdb>] kernel_thread_helper+0x7/0x10
>> Oleg, that's a fairly incomprehensible message we have in there.  Can you
>> please explain what it means?
> 
> Haha ok :-)
> 
> Good, since I run 2.6.20 with these debugging switches switched on, I
> get occasionally errors like these. I get ALWAYS the following error
> when the system first boots when the TOR executable is started:
> 
> [  137.324255] =======================================================
> [  137.324359] [ INFO: possible circular locking dependency detected ]
> [  137.324412] 2.6.20 #2
> [  137.324457] -------------------------------------------------------

Hi,

IMHO you should now switch off lockdep ("Lock debuging: ..." options),
until you update or get some patch for this circular problem.  Your
logs should be sufficient to nfsd people and lockdep turns off checking
after this anyway. I don't know if this is a known and real locking
problem, but it could be interesting now, if workqueue error would
reapear. It seems nfsd code is breaking somewhere with locks held -
maybe because of problems with lockdep's error handling.

Regards,
Jarek P.

-
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/