linux-kernel - Re: Major slab mem leak with 2.6.17 / GCC 4.1.1

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: <84144f020610122256p7f615f93lc6d8dcce7be39284@mail.gmail.com>
Date:	Fri, 13 Oct 2006 08:56:16 +0300
From:	"Pekka Enberg" <penberg@...helsinki.fi>
To:	"nmeyers@...tmark.com" <nmeyers@...tmark.com>
Cc:	linux-kernel@...r.kernel.org,
	"Catalin Marinas" <catalin.marinas@...il.com>
Subject: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1

On 10/13/06, nmeyers@...tmark.com <nmeyers@...tmark.com> wrote:
> If anyone has a version of kmemleak that I can build with 4.1.1, or
> any other suggestions for instrumentation, I'd be happy to gather more
> data - the problem is very easy for me to reproduce.

You should cc Catalin for that. Alternatively, you could try
CONFIG_DEBUG_SLAB_LEAK.
-
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/