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: <BANLkTik=M8uwnmHABqYBkeVDk56UMrnkMg@mail.gmail.com>
Date:	Thu, 12 May 2011 22:33:27 +0800
From:	ttlxzz ccc <boyzccc@...il.com>
To:	Américo Wang <xiyou.wangcong@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 答复: problem with kmemleak

Thanks for Wangcong

I have test the kmemleak-test.ko and the result includes no backtrace
except fffffffff, too.
I'm compling the kernel by make menuconfig. :)

If it still doesn't make sense, please help me again. Thank you.:)

On Thu, May 12, 2011 at 10:18 PM, Américo Wang <xiyou.wangcong@...il.com> wrote:
> On Thu, May 12, 2011 at 7:16 PM, Daniel Baluta <daniel.baluta@...il.com> wrote:
>>
>> Can you please remove your module?
>> I think the memory is leaked at unload time.
>>
>
> No, in kmemleak-test.c we have same examples.
>
> chenxi, I assume you didn't edit the .config manually?
> --
> 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ