All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.17-rc5 0/7] Kernel memory leak detector 0.3
Date: Tue, 30 May 2006 14:50:16 +0100	[thread overview]
Message-ID: <20060530135016.21491.34817.stgit@localhost.localdomain> (raw)

This is a new version (0.3) of the kernel memory leak detector. See
the Documentation/kmemleak.txt file for a more detailed
description. The patches are also available from
http://homepage.ntlworld.com/cmarinas/kmemleak/ (to be uploaded
shortly).

What's new in this version:

- more clean-up
- initial kernel modules support. It scans the data sections in a
  module while ignoring the text areas
- minor optimisation to avoid radix-tree lookup when updating
  the pointer information
- DEBUG_FS selected automatically (until/if a different method of
  triggering the memory scanning is implemented)

To do:

- better testing
- support for pointer aliases in kernel modules (i.e. container_of
  usage in modules)
- test Ingo's suggestion on task stacks scanning
- NUMA support

-- 
Catalin

             reply	other threads:[~2006-05-30 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30 13:50 Catalin Marinas [this message]
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 1/7] Base support for kmemleak Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 2/7] Some documentation " Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 3/7] Add the memory allocation/freeing hooks " Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 4/7] Add kmemleak support for i386 Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 5/7] Add kmemleak support for ARM Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 6/7] Remove some of the kmemleak false positives Catalin Marinas
2006-05-30 14:07 ` [PATCH 2.6.17-rc5 7/7] Simple testing for kmemleak Catalin Marinas
2006-05-30 14:17 ` [PATCH 2.6.17-rc5 0/7] Kernel memory leak detector 0.3 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=20060530135016.21491.34817.stgit@localhost.localdomain \
    --to=catalin.marinas@arm.com \
    --cc=catalin.marinas@gmail.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.