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 parent reply other threads:[~2008-12-30 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081219181255.7778.52219.stgit@pc1117.cambridge.arm.com>
2008-12-30 0:23 ` Andrew Morton [this message]
2008-12-30 11:43 ` [PATCH 00/14] Kernel memory leak detector 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$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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