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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 13 May 2011 15:08:57 +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 Fri, 2011-05-13 at 10:32 +0100, ttlxzz ccc wrote:
> I have tested kmemleak on the x86 and x86_64 architecture again. There
> is only
>  backtrace:
> 
>    [<ffffffffffffffff>] 0xffffffffffffffff
> 
> unreferenced object 0xffffc90012d27000 (size 64):
> 
>  comm "insmod", pid 13092, jiffies 4298369684
> 
>  hex dump (first 32 bytes):
> 
>    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
> 
>    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
> 
>  backtrace:
> 
>    [<ffffffffffffffff>] 0xffffffffffffffff
> 
> But in the x86, there is full backtrace.

Can you enable CONFIG_BACKTRACE_SELF_TEST and check whether the
boot-time backtrace test goes ok?

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