linux-kernel - Re: 答复: problem with kmemleak

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 16 May 2011 09:53:36 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	ttlxzz ccc <boyzccc@...il.com>
Cc:	Américo Wang <xiyou.wangcong@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 答复: problem with kmemleak

On Mon, 2011-05-16 at 08:18 +0100, ttlxzz ccc wrote:
> I'm very glad to find the reason of this problem. It's just because
> the CONFIG_FRAME_POINTER is not set :).
> 
> And in dump_stack() which is defined in arch/x86/kernel/dumpstack.c,
> CONFIG_FRAME_POINTER control whether to get the bp.
> 
> Now I enable CONFIG_FRAME_POINTER and I can see the full backtrace. :)

It's good you found it. I thought STACKTRACE on x86_64 would set the
necessary options like FRAME_POINTER so that it works properly. Kmemleak
only sets STACKTRACE.

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