mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: kmemleak: Pull request
Date: Thu, 11 Jun 2009 17:25:27 +0100	[thread overview]
Message-ID: <1244737527.13225.69.camel@pc1117.cambridge.arm.com> (raw)

Linus,

Please consider pulling the kmemleak patches from the branch detailed
below.

These patches have been posted/reviewed on several occasions on LKML and
available in the linux-next tree for about two kernel release cycles.
The necessary x86-specific patch is merged via the x86 tree and the
ARM-specific one via RMK's tree (these only add some vmlinux.lds.S
symbols).

Thanks.


The following changes since commit 991ec02cdca33b03a132a0cacfe6f0aa0be9aa8d:
  Linus Torvalds (1):
        Merge branch 'tracing-urgent-for-linus' of git://git.kernel.org/.../tip/linux-2.6-tip

are available in the git repository at:

  git://linux-arm.org/linux-2.6.git for-linus

Catalin Marinas (12):
      kmemleak: Add the base support
      kmemleak: Add documentation on the memory leak detector
      kmemleak: Add the slab memory allocation/freeing hooks
      kmemleak: Add the slob memory allocation/freeing hooks
      kmemleak: Add the slub memory allocation/freeing hooks
      kmemleak: Add the vmalloc memory allocation/freeing hooks
      kmemleak: Add kmemleak_alloc callback from alloc_large_system_hash
      kmemleak: Add modules support
      kmemleak: Remove some of the kmemleak false positives
      kmemleak: Enable the building of the memory leak detector
      kmemleak: Simple testing module for kmemleak
      kmemleak: Add the corresponding MAINTAINERS entry

 Documentation/kernel-parameters.txt |    4 +
 Documentation/kmemleak.txt          |  142 ++++
 MAINTAINERS                         |    6 +
 drivers/char/vt.c                   |    7 +
 fs/block_dev.c                      |    6 +
 include/linux/kmemleak.h            |   96 +++
 include/linux/percpu.h              |    5 +
 include/linux/slab.h                |    2 +
 init/main.c                         |    4 +-
 kernel/module.c                     |   56 ++
 lib/Kconfig.debug                   |   32 +
 mm/Makefile                         |    2 +
 mm/kmemleak-test.c                  |  111 +++
 mm/kmemleak.c                       | 1498 +++++++++++++++++++++++++++++++++++
 mm/page_alloc.c                     |   11 +
 mm/slab.c                           |   32 +-
 mm/slob.c                           |    7 +
 mm/slub.c                           |    5 +-
 mm/vmalloc.c                        |   30 +-
 19 files changed, 2049 insertions(+), 7 deletions(-)
 create mode 100644 Documentation/kmemleak.txt
 create mode 100644 include/linux/kmemleak.h
 create mode 100644 mm/kmemleak-test.c
 create mode 100644 mm/kmemleak.c

-- 
Catalin


             reply	other threads:[~2009-06-11 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 16:25 Catalin Marinas [this message]
2009-06-11 21:21 ` Linus Torvalds
2009-06-12  9:53   ` Catalin Marinas
2009-06-12  9:55     ` [PATCH 1/2] kmemleak: Remove the kmemleak.h include in drivers/char/vt.c Catalin Marinas
2009-06-12 12:07       ` Alan Cox
2009-06-12  9:55     ` [PATCH 2/2] kmemleak: Add more info to the MAINTAINERS entry 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=1244737527.13225.69.camel@pc1117.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®