linux-kernel - Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected

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]

Date:	Wed, 06 Sep 2006 00:27:08 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Andrew Morton <akpm@...l.org>, Miles Lane <miles.lane@...il.com>,
	linux1394-devel@...ts.sourceforge.net,
	LKML <linux-kernel@...r.kernel.org>,
	Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible	recursive	locking
 detected

Arjan van de Ven wrote:
> On Tue, 2006-09-05 at 21:23 +0200, Stefan Richter wrote:
>> This information confuses me. These places are not supposed to be the
>> ones where the locks were actually acquired, are they?
> 
> they should be yes
> (but inlined functions get the name of the function they are inlined
> into)

Was there function inlining performed? E.g. on those functions that are
called from only one place?
-- 
Stefan Richter
-=====-=-==- =--= --==-
http://arcgraph.de/sr/
-
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/