From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: [PATCH 00/14] Kernel memory leak detector
Date: Mon, 29 Dec 2008 16:23:10 -0800 [thread overview]
Message-ID: <20081229162310.705a25fe.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081219181255.7778.52219.stgit@pc1117.cambridge.arm.com>
On Fri, 19 Dec 2008 18:12:56 +0000
Catalin Marinas <catalin.marinas@arm.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?
next prev parent reply other threads:[~2008-12-30 0:23 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 18:12 [PATCH 00/14] Kernel memory leak detector Catalin Marinas
2008-12-19 18:13 ` [PATCH 01/14] kmemleak: Add the base support Catalin Marinas
2008-12-19 20:08 ` Pekka Enberg
2008-12-19 22:02 ` Ingo Molnar
2008-12-19 22:14 ` Andrew Morton
2008-12-22 13:05 ` Catalin Marinas
2008-12-30 0:23 ` Andrew Morton
2008-12-30 7:38 ` Ingo Molnar
2008-12-30 7:44 ` Andrew Morton
2008-12-30 7:52 ` Ingo Molnar
2008-12-30 7:59 ` Andrew Morton
2008-12-30 10:48 ` Catalin Marinas
2008-12-19 18:13 ` [PATCH 02/14] kmemleak: Add documentation on the memory leak detector Catalin Marinas
2008-12-19 18:30 ` Randy Dunlap
2008-12-19 18:13 ` [PATCH 03/14] kmemleak: Add the slab memory allocation/freeing hooks Catalin Marinas
2008-12-19 20:05 ` Pekka Enberg
2008-12-19 18:13 ` [PATCH 04/14] kmemleak: Add the slob " Catalin Marinas
2008-12-19 18:13 ` [PATCH 05/14] kmemleak: Add the slub " Catalin Marinas
2008-12-19 20:05 ` Pekka Enberg
2008-12-19 18:13 ` [PATCH 06/14] kmemleak: Add the vmalloc " Catalin Marinas
2008-12-19 18:13 ` [PATCH 07/14] kmemleak: Add kmemleak_alloc callback from alloc_large_system_hash Catalin Marinas
2008-12-19 18:13 ` [PATCH 08/14] kmemleak: Add modules support Catalin Marinas
2008-12-19 18:13 ` [PATCH 09/14] x86: Provide _sdata in the vmlinux_*.lds.S files Catalin Marinas
2008-12-19 18:13 ` [PATCH 10/14] arm: Provide _sdata and __bss_stop in the vmlinux.lds.S file Catalin Marinas
2008-12-19 18:13 ` [PATCH 11/14] kmemleak: Remove some of the kmemleak false positives Catalin Marinas
2008-12-19 20:15 ` Pekka Enberg
2008-12-22 12:04 ` Catalin Marinas
2008-12-19 18:14 ` [PATCH 12/14] kmemleak: Enable the building of the memory leak detector Catalin Marinas
2008-12-19 18:14 ` [PATCH 13/14] kmemleak: Simple testing module for kmemleak Catalin Marinas
2008-12-19 18:14 ` [PATCH 14/14] kmemleak: Add the corresponding MAINTAINERS entry Catalin Marinas
2008-12-30 0:23 ` Andrew Morton [this message]
2008-12-30 11:43 ` [PATCH 00/14] Kernel memory leak detector Catalin Marinas
2009-01-08 22:45 ` Andrew Morton
2009-01-12 9:51 ` Catalin Marinas
2009-01-12 10:21 ` Andrew Morton
2009-01-12 10:33 ` Stephen Rothwell
2009-01-12 11:13 ` Catalin Marinas
2009-01-14 12:30 ` Catalin Marinas
2009-01-14 14:01 ` Stephen Rothwell
2009-01-14 14:50 ` Catalin Marinas
2009-01-15 22:09 ` Mike Snitzer
2009-01-16 9:22 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2009-04-24 16:40 Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081229162310.705a25fe.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox