linux-kernel - Re: [2.6.32-rc3 kmemleak] WARNING: at kernel/lockdep.c:3161check

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: <1255005738.6715.6.camel@pc1117.cambridge.arm.com>
Date:	Thu, 08 Oct 2009 13:42:18 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
Cc:	paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [2.6.32-rc3 kmemleak] WARNING: at
	kernel/lockdep.c:3161check_flags+0xbe/0x180()

On Thu, 2009-10-08 at 21:34 +0900, Tetsuo Handa wrote:
> If the stack dump is correct, this error indicates circular function calls.
> We need to find the location which triggers circular memory allocation.
> Maybe just checking for NULL is not sufficient.

The circular function call is expected, nothing to do with the NULL
checking. You get callbacks from the slab allocator into kmemleak which
also allocates memory (but this latter call isn't traced - similar
behaviour in kmemtrace).

-- 
Catalin

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