| 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
| ||
|
Message-Id: <20081229162310.705a25fe.akpm@linux-foundation.org> Date: Mon, 29 Dec 2008 16:23:10 -0800 From: Andrew Morton <akpm@...ux-foundation.org> To: Catalin Marinas <catalin.marinas@....com> Cc: linux-kernel@...r.kernel.org, linux-next@...r.kernel.org Subject: Re: [PATCH 00/14] Kernel memory leak detector On Fri, 19 Dec 2008 18:12:56 +0000 Catalin Marinas <catalin.marinas@....com> wrote: > A new kmemleak version is available. Thanks to all who reviewed the code > and provided feedback. There are a largeish number of trivialish rejects against all the pending 2.6.29 code. Fairly easily fixed. I merge these patches into my tree, but I'd like to drop them again ;) > Kmemleak can also be found on this git tree: > > git://linux-arm.org/linux-2.6.git kmemleak Please prepare and maintain a tree for inclusion in linux-next shortly after 2.6.29-rc1 is released. What is the track record of this code? Has it found many leaks? Do we expect that it will find sufficient leaks of sufficient importance to justify kmemleak's inclusion and maintenance? I'm a little doubtful personally. We often fix leaks, and they are almost always things which nobody noticed at runtime, and which were found by code inspection or source-code checking tools. And they're usually leaks which nobody would care about much anyway? -- 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