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]

Message-ID: <BANLkTim0OGhBV4Ut81C3twKOBBjxUnkczQ@mail.gmail.com>
Date:	Thu, 12 May 2011 18:04:51 +0800
From:	ttlxzz ccc <boyzccc@...il.com>
To:	Maxin B John <maxin.john@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: problem with kmemleak

I am chenxi, too :)

On Thu, May 12, 2011 at 5:44 PM, Maxin B John <maxin.john@...il.com> wrote:
> Hi,
>
> Could you please share some more information about your setup ?
>
> Regards,
> Maxin
>
> On Thu, May 12, 2011 at 4:13 AM, ttlxzz ccc <boyzccc@...il.com> wrote:
>> help~~~：） please ！thx！！
>>
>> On Thu, May 12, 2011 at 10:06 AM, ttlxzz ccc <boyzccc@...il.com> wrote:
>>> Hi, all:
>>>
>>>
>>>
>>> I just want to use kmemleak, so I make the CONFIG_DEBUG_KMEMLEAK and
>>> CONFIG_DEBUG_FS on, mount the debugfs.
>>>
>>> But when I insmod mm/kmemleak-test.ko, echo scan >
>>> /sys/kernel/debug/kmemleak and cat /sys/kernel/debug/kmemleak. I just
>>> see this:
>>>
>>> unreferenced object 0xffffc90012d21000 (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
>>>
>>> unreferenced object 0xffffc90012d24000 (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
>>>
>>> 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
>>>
>>> There is no other backtrace except [<ffffffffffffffff>]
>>> 0xffffffffffffffff. Then I read the mm/kmemleak.c. In
>>> kmemleak_seq_show(), I find that the object->trace_len is 1.
>>>
>>>
>>>
>>> How can I get the full backtrace?
>>>
>> --
>> 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/
>>
>
--
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/