mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-kernel@vger.kernel.org
Cc: Dave Jones <davej@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Sergey Senozhatsky <sergey.senozhatsky@mail.by>
Subject: [PATCH 0/4] Kmemleak improvements on false positives
Date: Fri, 26 Jun 2009 15:12:35 +0100	[thread overview]
Message-ID: <20090626140847.31504.79381.stgit@pc1117.cambridge.arm.com> (raw)

Hi,

This set of patches are aimed at reducing the amount of false positives
and the verbosity of the kmemleak reports. The task stack scanning is no
enabled by default but this can be disabled at run-time with a risk of
more false positives.

I haven't looked into Sergey's function filtering patch yet.

Thanks for your comments.


Catalin Marinas (4):
      kmemleak: Slightly change the policy on newly allocated objects
      kmemleak: Do not trigger a scan when reading the debug/kmemleak file
      kmemleak: Simplify the reports logged by the scanning thread
      kmemleak: Enable task stacks scanning by default


 Documentation/kmemleak.txt |   19 ++++--
 mm/kmemleak.c              |  144 +++++++++++++++++---------------------------
 2 files changed, 67 insertions(+), 96 deletions(-)

-- 
Catalin

             reply	other threads:[~2009-06-26 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 14:12 Catalin Marinas [this message]
2009-06-26 14:12 ` [PATCH 1/4] kmemleak: Enable task stacks scanning by default Catalin Marinas
2009-06-26 14:12 ` [PATCH 2/4] kmemleak: Simplify the reports logged by the scanning thread Catalin Marinas
2009-06-26 14:12 ` [PATCH 3/4] kmemleak: Do not trigger a scan when reading the debug/kmemleak file Catalin Marinas
2009-06-26 14:12 ` [PATCH 4/4] kmemleak: Slightly change the policy on newly allocated objects 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=20090626140847.31504.79381.stgit@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --cc=sergey.senozhatsky@mail.by \
    /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

all inboxes | Powered by JetHome®